Jump to content

Search the Community

Showing results for tags 'tls'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 2 results

  1. I have XP SP3 updated under the guise of "faux POS" (not all updates applied though) Lately I find some cases - more and more often - of HTTPS sites that : - under XP, won't open in Chrome (nor IE), i.e. using Windows own crypto API - but that - - will open under Firefox - which has its own crypto stuff - even a very old version (3.5) works ! - under Seven, for compare, same sites do open even in Chrome (or, God forbid! IE). An example page there exhibiting the phenomenon : https://www.aidanwoods.com/blog/faulty-login-pages/ Is it expected with fully updated XP SP3 and/or "POS" windows ? Or have I missed a related update ? For reference I have : crypt32.dll version : 5.131.2600.6459 (xpsp_sp3_qfe.131005-0434) and rsaenh.dll : 5.1.2600.6924 (not that I'm half sure those particular dll's are the keys of the problem)...
  2. I've read a few posts on this forums about TLS support under Windows XP and i've just stumbled upon Stunnel, which is a proxy designed to add TLS encryption functionality to existing clients and servers. I don't know if this can solve the TLS issue under XP, but here you go to learn more about Stunnel. And here is the latest version (5.49) for Windows XP (32 bits).
×
×
  • Create New...