Leaderboard

Another set of links to Adobe Flash Player 32.0.0.156 release with SHA-1 signature which can be verified under Windows XP SP3/Windows XP x64 SP2 Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.156/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.156/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.156/install_flash_player_ppapi.exe

The official end of support may be near, but they'll have to pry my XP keyboard from my cold dead hands.

The cryptography 2.6.1 module with OpenSSL -1.1.1b (thanks to @Mathwiz) for Python 3.4.4 I have tested so far with the following modules: altgraph==0.16.1 appdirs==1.4.3 asn1crypto==0.24.0 cffi==1.12.2 colorama==0.4.1 cryptography==2.6.1 future==0.17.1 idna==2.8 macholib==1.11 packaging==19.0 pefile==2018.8.8 pyasn1==0.4.5 pycparser==2.19 PyInstaller==3.4 pyOpenSSL==19.0.0 pyparsing==2.3.1 PySocks==1.6.8 pywin32==221 pywin32-ctypes==0.2.0 six==1.12.0 urllib3==1.24.1 For Installing: Uninstall the older cryptography module beforehand (pip uninstall cryptography), then simply unpack the two directories in the python directory python34\lib\site-packages. Download (The latest cryptography module 2.7.dev1 from March, 11 2019 for testing is also included) Note: The manually installed cryptography module can be uninstalled the usual way (pip uninstall cryptography)!

Standard release channel for Adobe Flash Player has been updated today to 32.0.0.156. The standard SHA 256 installers are confirmed working on Windows XP SP3. https://get.adobe.com/flashplayer/otherversions/ Chrome 45 and newer, and Opera (Chromium) (PPAPI): https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ppapi.exe Chrome 44 and older, Opera (Presto) and Mozilla Firefox (NPAPI): https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player.exe Internet Explorer: https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ax.exe Uninstaller: https://fpdownload.macromedia.com/get/flashplayer/current/support/uninstall_flash_player.exe

Trying to build it now. Despite the fact that I'm building on WinXP, I still had to explicitly tell it to build for WinXP: perl Configure VC-WIN32 -D_WIN32_WINNT=0x0501 Without the -D just about every test failed; apparently the stupid Configure script just assumes Win 7+ rather than grabbing the version it's actually running on . That may explain why so many of the "compatible with XP" builds aren't actually compatible with XP. Edit: Final (apparently XP-compatible) build of OpenSSL v1.1.1b is about 3 MB when written to a .7z archive file. You can download it from my company's Web site.

XP still seems fresh as a daisy compared to the wilting goutweed that is Windows 10.

Almost. (I assume that unlike me, you have a full version that will not expire!) You also need Perl and NASM. I used Strawberry Perl, available from http://strawberryperl.com. NASM is available from https://www.nasm.us. Both are free. After installing them, make sure both are in your PATH. Edit: I forgot to mention; once you install Perl you need to install the "Text::Template" module. To do this, enter the command cpan Text::Template I created OpenSSL with all default options, except for forcing XP compatibility. VSE 2010 puts a "Visual Studio Command Prompt" on the Start menu. It runs a batch file that sets up the necessary environment variables. I selected that, then ran these commands: $ perl Configure VC-WIN32 -D_WIN32_WINNT=0x0501 $ nmake $ nmake test $ nmake install nmake is part of VS2010. The '$' above stands for the C:\> command prompt. The final build was placed in C:\Program Files\OpenSSL. Unix and OpenVMS support a "no-shared" config option. I didn't try that for this Windows build, but if it works, I assume everything would be built into the .lib files and no .dll files would be built, which I believe is how the Cryptography developers intended it.

That does not work. The size of the lib files in your package seemed very small, but I leave no stone unturned. For the missing parts in the lib files (have landed at the files libcrypto-1_1.dll, libssl-1_1.dll and possibly also at capi.dll, padlock.dll) there must be a reference in the lib files to the dll files Especially since without these files an error message from HTTPSProxy is issued because of missing dll files. Part of VS2010 is needed to build the cryptography module in Python 3.4.4 (Microsoft Windows SDK (for Windows 7) DVD (GRMSDK_EN_DVD.iso), maybe the VS2010 on this DVD is enough to create OpenSSL?). Therefore, the files from the Include folder are also needed. If you look at the size of the generated _openssl.pyd file in the newly created Cryptography modules, that is noticeable. I'm glad it works that way because it keeps the puzzle for TLS1.3 moving forward. The users who use Python version 3.5 or higher need a build with VS2015! The Cryptography module would therefore have to be created under Windows 7 (parts of VS2015 are needed) with your customized OpenSSL variant and hope that this module now works under Windows XP.

Updates from March 2019 are out! Direct links for POSReady 2009 updates (13 updates, English Only) and IE8 cumulative critical security update (English) http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/02/windowsxp-kb4486468-x86-embedded-enu_491ec2dcd578becacf2ec08f65b6c6f62ca3822c.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4486536-x86-embedded-enu_4dd89d4cfab9ba6526747646e320adf407b6ece4.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/02/windowsxp-kb4486538-x86-embedded-enu_b46b867293bb21b12fe5867ff98806a98ae50fa2.exe http://download.windowsupdate.com/d/msdownload/update/software/uprl/2019/02/windowsxp-kb4487989-x86-embedded-enu_3c32c4f284fcd7208b3cf4428320e95a27513c3a.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4489493-x86-embedded-enu_bf5786db231541e562a8f4dececac9b8fdc3cdce.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/02/windowsxp-kb4489973-x86-embedded-enu_1c50f081b27c440d89300b59cd5df9ed689390b0.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4489974-x86-embedded-enu_fb9d178e51321bf47246a752c2d79dcfe6bada40.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/03/windowsxp-kb4489977-x86-embedded-enu_e1b835d2c684f2953946a414fddc7fe40ef6eec2.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4490228-x86-embedded-enu_a81c03f3f775390169d890d6f99cd9d3e58cc62e.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4490385-x86-embedded-enu_47b193ff117da1c86efc4d275b52a829c5cb00b9.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/03/windowsxp-kb4490500-x86-embedded-enu_cf8ce2e609b0ba3649e6def41602329a7ab2a6fc.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/02/windowsxp-kb4490501-x86-embedded-enu_c0b31474df5c52c3f1794914050fdf27b0692c65.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/03/windowsxp-kb4493341-x86-embedded-enu_cfd32e1875c216557e94e1763fbc114c216d6b0c.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/03/ie8-windowsxp-kb4489873-x86-embedded-enu_71a78302b04573b88909c6550d0e51166c15c19f.exe

I think this is even better than the original! With the original Cryptography, we had to wait for the Python developers to release a new Cryptography version, incorporating the latest OpenSSL. With your version, we only need to replace the .dll's in C:\Python34\Lib\site-packages\cryptography\hazmat\bindings. Unfortunately, the copy of MS Visual Studio Express 2010 I used to build OpenSSL is set to expire in 25 days, and M$ no longer provides free registration for VSE 2010 or 2012. For VSE 2008, there was a simple workaround involving deleting a registry key, but it doesn't seem to work for VSE 2010. So I'll probably have to install VSE 2015 (along with Perl and NASM) on the Win 7 side in order to build OpenSSL when 1.1.1c comes out.

I was able to create a working Cryptography (2.6.1) module for Python 3.4.4 , but the two binaries libcrypto-1_1.dll and libssl-1_1.dll are required. Had to improvise something (is not in the sense of Cryptography module creator), it works and that's the main thing. Now I will do several tests (when the tests are completed, I will make this module available). Thanks a lot!

Done!

Win 10 is a rolling disaster. Win 8 (and, I assume, 8.1) aren't bad as long as you install Classic Shell so you don't have to deal with the "Metro" UI. With Win 8, you can get WMC for the Pro version, and IIRC there's even a Web site where you can get Win 7's "gadgets" back. (Gadgets were removed in 8 for "security;" IOW, M$ didn't want to deal with patching any security holes that might crop up, so they just dropped gadgets in Win 8 entirely. Ironic since Win 7 & its gadgets are supposedly supported for another year.) I think Win 7 Pro is the last version with "XP Mode" (XP in a VM), though. If you have 7 Pro, grab XP mode while you can; it's still the best solution for folks needing XP for older programs and 7+ for newer ones!

The update that was supposed to bring version 1809 closer to the state in which it should've been released in the first place. Didn't seem to accomplish the goal. Am I too optimistic by assuming that was the goal? The frequency of new feature updates should really be reduced. What's the point of releasing a bugged OS every 6 months, only for it to take another 6 months at least to fix it when another bugged build is released into the wild?

Both of these appear to be free of bcrypt.dll dependencies, proving one can build OpenSSL 1.1.1 that works on Windows XP. The build from the Curl for Windows project also includes the /include and /lib subdirectories; I think these are required because the Cryptography module is a static build; i.e., instead of loading the OpenSSL .dll's when called, the OpenSSL code is included when Cryptography itself is built. (IOW, to build Cryptography we don't need the .dll's; we need the same code in lib format.) However, there is a difference in naming between the Curl for Windows /lib files and the Cryptography project's /lib files. The former have .a extensions while the latter have .lib extensions. I'm guessing this reflects a difference between the MinGW compiler (uses .a) and MSVC (uses .lib). Not sure if the different extensions imply a different format for the lib files. To be safe I suppose it would be best to rebuild OpenSSL 1.1.1b with MSVC. Looks like a complex build though; you'll need: I didn't see a 32-bit version of ActiveState Perl on their website, but there is a 32-bit version of Strawberry Perl and of NASM, so it should be possible to build OpenSSL on a 32-bit system with MSVC. The .LIB files mentioned above are included with VS 2010 (and presumably VS 2015 also). Good luck!

Windows 10 is also very un-customizable compared to XP, which basically blasted the door open on UI skinning. You had many options available if Luna or Windows Classic didn't suit your tastes (even a few direct from MS). Even if you manage to restore some sanity to the look of 10, an update comes along and wrecks your hard work, as well as altering many of your settings, crushing your anti-telemetry safeguards and rearranging the UI like the chairs on the deck of the Titanic.

New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.1.1-Goanna-20190309.7z Changelog: Out-of-tree changes: * update Goanna3 to git d0444154b..804907cdb: - import changes from rmottola/Arctic-Fox: - Bug 1135903 - OdinMonkey: Check the siginfo si_code field before handling a SIGSEGV (e5452f1ac) - Bug 1112164 part 5 - Distinguish between the FloatRegister code and the encoding on x86 & x64. (7e27e254d) - Bug 1152176 - xpcom: Define linux kernel BLOCK_SIZE if necessary. (4ff9c701e) (804907cdb) * Notice: the cha ngelog above may not alw ays applicable to XUL Runner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190309-804907cdb-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190309-804907cdb-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190309-804907cdb-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190309-804907cdb-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - Bug 1135903 - OdinMonkey: Check the siginfo si_code field before handling a SIGSEGV (e5452f1ac) - Bug 1112164 part 5 - Distinguish between the FloatRegister code and the encoding on x86 & x64. (7e27e254d) - Bug 1152176 - xpcom: Define linux kernel BLOCK_SIZE if necessary. (4ff9c701e) (804907cdb)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190309-7e0d3b80f-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190309-7e0d3b80f-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190309-7e0d3b80f-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190309-7e0d3b80f-xpmod.7z Official repo changes since my last build: - Add hover state arrow images. (c8ef59dae) - Remove updater gunk from the about box. (a61164a88) - Replace about box backdrop. (7f6137983) - Update about box design. (f0c57ac5f) - Fix dynamic addition of build date. (97be0f65c) - [Basilisk] Add Netflix SSUAO to work around blocking behavior for EME DRM-enforcement for later Firefox versions. (fd3692657) - Remove texture layout endian-ness check for Moz2D. (b55a0dd24) - Tweak the about box layout a bit. (a7bca40ad) - Tweak the about box styling some more and clean up styles. (403605efb) - Adjust Pale Moon™ wordmark for better contrast (a49d052af) - Merge pull request #985 from MoonchildProductions/aboutbox-redesign (5dba1ebe8) - Remove e10s code from browser widget. (083d322b7) - Don't include nsDownloadManagerUI if the Communicator version is used (853fe00ba) - [PALEMOON] Fix updatesSeparator id mismatch (baeec92b6) - Revert "Don't include nsDownloadManagerUI if the Communicator version is used" (011610259) - Don't include nsDownloadManagerUI if the Communicator version is used (7e0d3b80f)

Legacy version 1.16.4.9 of uBO is available. Appears to be a cosmetic fix with positioning the uBO button in the toolbar. I had mixed success with uBO Updater. It worked a treat in Serpent 55, offering 1.16.4.9 vs. 1.18.4 (or whatever the most recent stable version is). But in Serpent 52 it didn't offer me an update at all. Had to go into the releases at Github and download/install 1.16.4.9 manually. Edit: This is probably related to the upstream changes made to Basilisk, to check for updates at addons.basilisk-browser.org vs addons.mozilla.org, but uBO Updater is supposed to intercept those checks anyway