Leaderboard

Well, the title of this thread (in the form of a question) is a tad misleading ; if the real question was Can you establish TLS 1.3 connections under Windows XP? then the answer, of course, is YES . Both UXP browsers (New Moon 28, Serpent 52.9.0), the Moebius fork (Serpent 55.0.0), the Tycho fork (New Moon 27) and probably other @roytam1's forks all support the final TLS 1.3 draft (RFC8446), as well as all three cipher suites associated with TLS 1.3: TLS_AES_128_GCM_SHA256 (0x1301) TLS_AES_256_GCM_SHA384 (0x1302) TLS_CHACHA20_POLY1305_SHA256 (0x1303) ; you can test TLS 1.3 support of these browsers with https://tls13.pinterjann.is/ https://swifttls.org/ https://cert-test.sandbox.google.com/ (and a few other test URLs...). BTW, the NSS library in these browsers was recently downgraded from v3.44 Beta to v3.43 stable release; perhaps @roytam1 could share a word (or two ...) why that was necessary ... Additionally, I was recently informed that the excellent project ProxHTTPSProxy by @heinoganda has indeed achieved TLS 1.3 support under XP for the type of browsers (IE8, Google Chrome 49 and, possibly, earlier) that don't come with their own TLS support but rely upon system libraries for secure connections; so TLS 1.3 in itself shouldn't be an issue... But what is indeed specific is the configuration of linked test server, https://tls13.1d.pw/ It is no coincidence that a Russian member of this forum brought this up, because, it turns out that, the administrator of said test server is a Russian guy, Александр Венедюхин ! In fact, he maintains a blog where he documents this project and the TLS 1.3 test configuration of the server; original articles can be found at: https://dxdt.ru/2018/08/05/8597/ https://dxdt.ru/2019/01/26/8672/ As I'm not at all fluent in Russian (), I had to enlist the help of (evil ) Google, but what the heck... : https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ I don't consider myself proficient in the field of cryptography and/or secure connections, but what I gathered from the translated text was that the server is configured to send a special HelloRetryRequest response to force a renegotiation of connection parameters; the implementation of Encrypted Server Name Indication (ESNI) along with non-ECDH manifested a bug in Mozilla's NSS library, so that is probably why the Firefox forks won't connect currently to that specific test server! (they yield a SSL_ERROR_RX_MALFORMED_SERVER_HELLO error code ). Hopefully, the reported bug will be fixed in a future NSS version, if/when that is applied to UXP, we'll have successful connection in the UXP forks... Frankly, TLS 1.2 is still predominant, but with 1.3 steadily gaining ground; this specific connection test is but a margin case where 1.3 is involved, so I won't be losing any sleep over it...

I contacted him and he replied. Please note that his very first release release is expected to run on Windows 7 and above as it's just a test, so it will not on XP and Vista as there are many missing kernel calls. Even by linking it to our modified kernel there are still QueryThreadCycleTime, SHGetKnownFolderPath, SetProcessDPIAware, and an API API-MS-WIN-CORE-SYNCH-L1-1-0.DLL which makes use of OpenProcess which will prevent it to run on XP. I sent to him our code stored on GitHub and some of our compiled binaries, although I didn't send the compiled version of Chromium yet, but he'll be able to access it soon as I'm gonna add him to the Windows XP Forever group. C'mon guys, let's make this flipping browser run! EDIT: On an unrelated note, I'm trying Chrome 360, but it's asking me for a 360 Account. Can't I just log in with my google account? Is there a way to link those two? EDIT: Some messages about the CPU and other stuff are still in Chinese. Is there a way to get them in English?

The latest version of Qihu's 360 Extreme Explorer (v11.0.2086.0, released May 16th 2019 - its default UA declares a Chromium 69.0.3497.100 compatibility ) will also pass the test : But this is on Windows Vista SP2 32-bit, not on XP SP3 32-bit (hence, one of you XP users would have to test... ) EDIT: Make sure in "flags" that chrome://flags/#tls13-variant is set to "Enabled (Final)"

Doesn't seem to matter though. I never claimed (or implied) that staying at NSS 3.44 Beta (instead or reverting to 3.43 Stable) would have allowed for the UXP browsers to successfully connect to the linked test server, i.e. https://tls13.1d.pw As I was already talking about the NSS library, I simply found an opportunity to mention the version downgrade I had observed; just that ... Today I borrowed briefly sister's Windows 7 SP1 64-bit laptop, where I updated stable Firefox (Quantum) to latest release 67.0 and Firefox ESR (Quantum) to latest release 60.7.0; to my great astonishment, both these Firefox versions connect successfully to the TLS 1.3 test server being discussed in this very thread; I dug around and found v60.7.0 comes with NSS 3.36.7, while v67.0 comes with NSS 3.43, the same one to be found inside the latest UXP forks released by Roy; so, despite my initial assessment, the "bug" observed here ("SSL_ERROR_RX_MALFORMED_SERVER_HELLO" error code when trying to connect to test server with latest New Moon 28/Serpent 52.9.0) doesn't appear to be only dependent on used NSS version and has been already fixed in latest Firefox Quantum releases! I persevered with my searches and, in the end, I stumbled upon a similar issue that was also affecting the Waterfox fork: https://github.com/MrAlex94/Waterfox/issues/783#issuecomment-458907249 So it looks as though the proper fix for this issue lies inside Bugzilla bug #1430268 fixed in mercurial commit: https://hg.mozilla.org/mozilla-central/rev/fafb731 @roytam1: Do you think you can somehow backport bug #1430268 to the UXP platform and thus apply it to both NM28/St52? Is a test-build even possible? If yes, then the OP (@Bersaglio) won't have to use a Chinese browser to connect with... OT: I don't mistrust myself the Chinese browsers any more than I do American ones like Google Chrome or Russian ones like Yandex Browser; all government security agencies are pretty much the same in my eyes... ; in this day and age, there's no such thing as privacy if you decide to connect to the live web...

Good luck! The Office 2007 Compatibility Pack doesn't officially work on Windows 98, but I did get it to install, and it will allow you to read (I don't know about write) .docx Word documents in Windows 98. There's a bigger problem with newer Excel and PowerPoint files unfortunately.

The default setting is ambiguous "default". I think that there should be no problems if there is no Google account entry in the browser itself. Or it is hidden. But I still turned off this option.

@VistaLover Thanks for the info, just checked 360 Extreme Explorer 11.0.2086.0 (Chrome 69) on the XP SP3 virtual machine and TLS 1.3 passes the test via specified test server. But sadly it is not an option for me because I never trust Chinese browsers due to privacy concerns... This is not correct. I used official Mozilla test server https://tls13.crypto.mozilla.org/ until it was taken down without any warnings or explanations. Then I started looking for a similar test server and found one linked in the first message of this topic. I didn't even know who is the administrator of this server, but its domain name doesn't look related to Russian Internet segment.

@Dave-H I found the cause of why when FF launches it kept asking me to install a addon again in the profile there was a extention folder with extentionds in, these were what i was being asked to install again I removed that it seems now they stick, and I don't get asked again Hoping lol

I don't have an 360 Account and was never asked to create one.. When does it ask for it?

Guys, I found an application that requires .NET Framework 4.7.2 - dnSpy is .NET debugger and assembly editor. https://github.com/0xd4d/dnSpy And yes, it works on Vista! Unfortunately, I'm not yet so cool to use it. Portable application. Does not require installation.

because it crashes.

Very first post: These prefs don't really matter when running FF 52.9 on WinXP, since it's been coded to block e10s on XP unless browser.tabs.remote.force-enable is set to true - in which case e10s is enabled irrespective of these other prefs. These prefs do matter on later Windows versions (and are the preferred method of enabling e10s) but let's stick with FF 52.9 on XP for now. Once e10s is enabled, this controls how many additional processes you can have. There's one "core" process plus one process per open tab up to the limit set by this pref. Personally, I set dom.ipc.processCount to 2. The default of 1 gives me little benefit, but larger values just waste RAM while providing little additional benefit, at least in my experience. But as usual, YMMV.

Good. Meanwhile, 360 Chrome is working OK, and actually can display correctly things well beyond Serpent 52. Even if not perfectly compatible with Chromium 69, it sure is way beyond Google Chrome 49, and that's pretty useful as it is.

It does seem to also work on Windows XP x64 SP2 with 360 Extreme Explorer, therefore it should work on all Windows XP editions.

IIRC it didn't even come with PIP installed. So you'll need to install it if you haven't done so already. (If you need to install it, there's a Python script get-pip.py that will do the job at https://bootstrap.pypa.io/get-pip.py. Download it and type py get-pip.py to run it.) Once installed, I'm pretty sure you run commands like 'pip help' from the Windows command line, not the Python command line:

This is most probably caused by the fact 4.6.2 Preview can be properly installed via the provided installer, while 4.6.2 Final can only be installed via a hack-ish way ; it is possible running just the .MSI (in the unpacked original setup) does not write all of the necessary registry keys and/or modify ENV VARs; most sadly, I'm not a coder so can't provide any substantial help, but googling the issue I found: https://stackoverflow.com/questions/5980847/visual-studio-2010-startup-type-initializer-for-module-threw-an-exception https://blogs.msdn.microsoft.com/rajakedar_ganta/2012/06/12/the-type-initializer-for-module-threw-an-exception/ Hope they make sense to you! Regards

Well https://wiki.beamng.com/Requirements says they do not support Vista or VMs. Was the game working before you installed Windows updates in April?

Here is an updated list of updates with links. Updates.zip

Seriously? That's dev speak, no normal user will have any clue what especially "upstream" means, and be confused yet more. And riddling what those mysterious other code sources or organizations might be.