AstroSkipper

The work is done. The ProxHTTPSProxy's PopMenu TLS 1.3 3V3 program package is ready and has been published by me. See here: Cheers, AstroSkipper

Hello to all users of my recently released program package ProxHTTPSProxy's PopMenu TLS 1.3 3V3! The last time, when I released ProxHTTPSProxy's PopMenu 3V1, the feedback was rather poor, i.e. almost non-existent. This time, I really need your feedback! Please, post your opinions, experiences, observations, further suggestions of improvement and so on! And, I would like to know whether you like my program package or not, and why! In any case, it was not an easy work, I changed many things, and I spent a lot of time to do that all. And you certainly know an author of software lives from the feedback of the users! Especially, when everything is provided free of charge! In any case, I am very curious about your posts. Thanks in advance! Cheers, AstroSkipper

I didn't give you only a version number, I said Firemin Portable in the version 6.3.1.5105. I already offered to upload this version one week ago, but you didn't reply. This version is not available in the internet and by using the Wayback Machine anymore, either. Anyway, the next time, I'll be running my desktop computer I'll upload this version for you and other users. Cheers, AstroSkipper PS: On Rizonesoft's download site, are always two versions offered, an installer and a portable version of Firemin.

The documentation of my program package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 has been corrected in regard to spelling, punctuation and grammar. The updated archive has already been uploaded. Cheers, AstroSkipper

Thanks for your finds! I already found them, too! Have been corrected! And I found a lot more! The name of the archive can have the same as one of its subfolder without any problems. After downloading, you can simply extract the complete archive to any folder. Its name doesn't matter using 7-Zip or WinRAR! Of course, you are not allowed to create two subfolders of the same name in one folder. Frankly, I neither extract files or folders to the desktop nor use the Windows feature "Extract to". This feature was disabled from the very first. Anyway, I can't reproduce that because there is no "Extract to" in my Windows XP. I tested extracting with 7-Zip, and there are no issues here. BTW, all file operations I have to perform in my system will be done by using a file manager, in my case Total Commander. I always download such files in my "Download Archive", located on another drive, and can do with them whatever I want to. I never download files into my system partition, I separate that very strictly. If you have 7-Zip installed, the easiest way is to double-click onto the archive and copy the folder "ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3" inside to any location by using the Explorer or a file manager. In Total Commander, it even works without 7-Zip! PS: You can rename my archive, too, of course!

No problem! Do it when you have time! You are my beta tester, and your opinion is very important for me! PS: And, I forgot to mention that in such long posts the extension Grammar and Spell Checker - LanguageTool stops working! It is limited to a number of words in the free version.

You're very welcome! Did you already try it? It was really hard work! But now, the windows of my programs react faster and behave more "professional", in my opinion, of course. What do you think?

Maybe, but I had problems with my computer, indeed! My Avast Prenier was totally broken, and I had to repair the installation. And in Mypal 68, MSFN had a lot of problems while editing my very long post. The built-in editor went totally crazy.

You're very welcome! PS: Sorry for double posting! My computer is totally screwed up today!

You're very welcome!

Release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 I am pleased to release my brand-new version of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 to the public. The main feature of my program package is @cmalex's ProxyMII, a TLS 1.3 proxy. I replaced @heinoganda's TLS 1.2 proxy from my last release of ProxHTTPSProxy's PopMenu REV3e 3V1 by @cmalex's TLS 1.3 proxy. This sounds simple, but, unfortunately, it wasn't. A lot of problems had to be solved to implement this proxy completely, enhance functionality, and get control of it as convenient as the old one. ProxHTTPSProxy's PopMenu is a one-click menu in systray to access and control the brand new TLS 1.3 proxy ProxyMII, better known as ProxHTTPSProxy, credits to @cmalex and its original creator whenever. All information about ProxHTTPSProxy can be found in my article: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1213600 which will be updated in the next time. @cmalex's ProxyMII, dated from 2022-07-17, is now based on OpenSSL 3.0.5 and Cryptography 3.4.8. It provides all TLS protocols from TLS 1.0 up to TLS 1.3 and its corresponding ciphers. ProxHTTPSProxy's PopMenu TLS 1.3 3V3 is the third release of ProxHTTPSProxy's PopMenu 3.0, now in version 3.0.0.0, shortened 3V3. It is a synthesis of the excellent, brand new TLS 1.3 proxy ProxyMII, dated from 2022-07-17, credits to @cmalex at MSFN, several self-programmed executables and a very few commands, credits to @AstroSkipper at MSFN, the freeware PopMenu 3.0, credits to Jochanan Agam at freeware.persoft.ch, the open source utility Min2Tray v1.7.9, credits to Junyx at junyx.breadfan.de, and the program Certificate Updater 1.6, credits to @heinoganda at MSFN. If you wonder when the second version was released, the answer is very simple: never. This version was unofficial. ProxHTTPSProxy's PopMenu is not a classical launcher, it is rather a systray pop-up menu. It can be totally customized and continuously extended according to the user's needs due to its modular structure, therefore, much more flexible than a classical, compiled launcher. More features can be added easily without touching the existent code. Due to ProxHTTPSProxy's PopMenu's modular structure, the user can change, add, delete and reorder features. Even the icons in the menu can be changed easily by the user. Here is a screenshot: System requirements: @cmalex's ProxyMII was created by Python 3.7.1 which requires Microsoft Visual C++ 2015 Redistributable or Microsoft Visual C++ 2015-2019 Redistributable (latest version 14.28.29213.0). Furthermore, Microsoft .NET Framework 4.0 is now required to run my program package. Check if both are installed in your system! A CPU with SSE2 instruction set is no longer required, SSE only is sufficient. Features of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: Here is the complete list of features implemented in ProxHTTPSProxy's PopMenu TLS 1.3 3V3 and a short explanation of them: Start ProxHTTPSPoxy – Activates the proxy's settings in IE LAN Settings, starts the proxy, and deactivates and cleans its settings after closing, all automatically. Stop ProxHTTPSPoxy – Stops the proxy and closes its status window. Minimize ProxHTTPSProxy to systray – Minimizes ProxHTTPSProxy's status window to systray and shows its icon there. Restore ProxHTTPSProxy from systray – Restores ProxHTTPSProxy's minimized status window from systray. Hide ProxHTTPSPoxy – Hides ProxHTTPSProxy's status window completely. Show ProxHTTPSPoxy – Shows ProxHTTPSProxy's hidden status window again. Check if ProxHTTPSPoxy is running (in RAM) – Checks if ProxHTTPSPoxy is running in the background. cacert.pem Update – Performs an update of the file cacert.pem. Root Certificates Update – Performs an update of the system's Root Certificates. Open IE Proxy settings – Opens the tab LAN Settings in IE's Internet Options. Close IE Proxy settings – Closes the tab LAN Settings and IE's Internet Options completely. Check system proxy status – Checks whether the proxy is used system-wide or the system has direct access. Enable ProxHTTPSProxy system-wide – Permits the whole system to use this proxy. In this mode, services can route their traffic through the proxy, too. Disable ProxHTTPSProxy system-wide – The proxy can be used only locally if it is running, generally all have direct access to their servers or the internet. Edit config.ini – Opens the file config.ini with the editor Notepad to check or modify the proxy's configuration. Read documentation – Opens the documentation with the editor Notepad to get quickly information. In the screenshot above, you can see a red arrow. This is the icon of ProxHTTPSPoxy, minimized to systray. It's a new feature, and the green marked items have been added to the pop-up menu since last release. ProxHTTPSPoxy's PopMenu is provided together with ProxyMII from 2022-07-17, created by @cmalex and branded by me as ProxHTTPSProxy 1.5.220717. This new archive called ProxHTTPSProxy TLS 1.3 1.5.220717 PopMenu 3V3 has been additionally updated by me. These are the changes to the previous version of ProxHTTPSPoxy's PopMenu: Changelog of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: @heinoganda's ProxHTTPSProxy REV3e replaced by @cmalex's ProxHTTPSProxy 1.5.220717 with a brand new TLS 1.3 support. New starter program StartProxy.exe created to activate the proxy settings, start the proxy, and deactivate its settings after closing, all automatically. cacert.pem updated to the most recent one. Alternative cacert.pem from Mozilla, updated to the most recent version dated 2022-07-19. The open source utility Min2Tray has been fully implemented by the new configuration tools Configure PopMenu.exe and Setup Min2Tray.exe, all automatically. After the setup procedure, the programs PopMenu and Min2Tray are started automatically. All self-created files are not UPX-compressed. Therefore, the version is a noUPX only. Two new items added to the pop-up menu: Minimize ProxHTTPSProxy to systray and Restore ProxHTTPSProxy from systray. All unnecessarily embedded files have been removed from my self-created executables. Changes in calling up other programs. In all my affected programs, protection against code injection has been improved. This leads to preventing of future "space bugs", too! Different issues, which could have been noticed only in very rare cases, have been fixed. All unnecessary code has been removed. New bugs I additionally found have been fixed. Autostart entries of PopMenu and the new Min2Tray, automatically added to the registry by my configuration program, have been fixed in regard to the "space bug". All message windows of my programs have been resized and adjusted for a better visibility. All my self-created program files have been recompiled by using a different compiler. @cmalex's original ProxyMII wasn't modified by me, except a replacement of ProxHTTPSProxy.EXE's program icon, back to the old one and an update of the file config.ini to get access to the Microsoft Updates (MU) website with this proxy. Installation and start of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: Check if Microsoft Visual C++ 2015 Redistributable or Microsoft Visual C++ 2015-2019 Redistributable (latest version 14.28.29213.0) is installed in your system. Check if Microsoft .NET Framework 4.0 is installed in your system. Unpack the archive and copy either the complete folder ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3 or its complete content to your desired location. Install the file CA.crt, located in the main program folder, to Trusted Root Certification Authority under the account local computer, or use the program ProxHTTPSProxy Cert Installer, provided in the archive. Go to the subfolder PopMenu and execute the program Configure PopMenu.exe. PopMenu and Min2Tray will be started automatically. A more detailed documentation, titled Documentation of ProxHTTPSProxy's PopMenu 3V3, can be found in the subfolder Docs of my program package and should be read before using ProxHTTPSProxy's PopMenu in any case. All features and more are described there. The programs PopMenu and Min2Tray have a very low usage of RAM. It's only about 2 MB and 4 MB respectively. And here is my release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: Download of ProxHTTPSProxy's PopMenu 3V3: Link: https://www.mediafire.com/file/4sqkixfd2waaypt/ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3_CheckedByAstroSkipper.7z/file Password: CheckedByAstroSkipper. All files in my archive are definitely virus-free and clean, although some AV scanners produce false positives. I recommend adding the complete folder to the exclusion list of your security program(s), only if you trust me, of course. Apart from that, you can also check positive reported files on VirusTotal, though. If you find a bug, need help, or have questions relating to this package, post it in the commenting zone of this thread here! And finally, we, @cmalex and me, would be very pleased about posting your experiences and opinions relating to ProxHTTPSProxy's PopMenu TLS 1.3 3V3. Any reactions by commenting, liking, and up-voting are welcome! All this can be done in my threads https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/ and https://msfn.org/board/topic/183684-looking-for-a-person-with-python-programming-skills-to-implement-tls-13-functionality-in-proxhttpsproxy-rev3e/. As you know, an author of software lives from the feedback of the users! Kind regards, AstroSkipper

Foreword and acknowledgements to the release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 First, I want to thank @cmalex for his efforts and work in regard to ProxyMII. Without his selfless act and his uploading of the proxy packages, my program package would not have been possible. We all know, he is Ukrainian, and they really have other things to worry about than programming stuff for our beloved, old OSes or helping here in the forum. Therefore, all the more remarkable! And a second big thanks for updating this proxy to the more recent OpenSSL 3.0.5 and Cryptography 3.4.8. This has made ProxyMII significantly much more future-proof. As I already said in another thread of mine, one cannot thank him enough! And this has to be said again and again! At next, I want to thank again my beta tester team, @Dave-H, @mina7601, @NotHereToPlayGames, @XPerceniol, and @George King! Thanks for your efforts and time commitment! You all and especially my core testers, @Dave-H, @mina7601, and @NotHereToPlayGames did a great job! Thanks for that! In any case, an early release of my program package would have been a disaster for sure! Many, many thanks!

Wow! You even speak German. Unbelievable!

You're very welcome! I do my very best! @VistaLover BTW, I thank you for the continous efforts in roytam1's browser thread in regards to your support, investigations, observations, and solutions! I read all your posts regularly!

And my file can be taken as an example of a completely clean one! Therefore, such files exist! Thanks for your tips! A lot of my posts, as for example in this moment, I write in Opera on my Android tablet. This browser version doesn't support extensions or spell-checking. Sometimes, I copy my content in the Deepl app I have recently installed. Much more effective is writing in Mypal 68. There, I have installed the extension Grammar and Spell Checker - LanguageTool. A perfect tool! I can definitely recommend it.

Hmmm..., the picture only shows which AV engines whitelisted the complete package, NOT which files inside the package were found to be benign, which, I believe, was what was actually queried by @Dave-H ... The picture shows the complete results of one file which meant to be clean by all of these AV scanners on VirusTotal. @Dave-H had doubted that such a thing even existed if I understood him correctly. ... English lesson of the day! Should've been: "Batch files themselves" (if you were going to use the plural number ) ... Thanks for the lesson of the day! Nice giveaway! I need that, and as always, you're absolutely right. But, as you can see I write most of these posts by myself without using translators. Just to improve my English! You're very welcome! I do my very best!

Here is the answer: Batch files themselves are less problematic than compiled executables from batch files, especially with hidden windows.

Anyway, all Windows XP compatible AV engines on VirusTotal do not generate false positive reports anymore! And, nearly all established and well-known AV scanners, too! Except Kaspersky, but I never trusted this company in the past, and will never trust it again in terms of security for good and well-known reasons.

Good question! I am the creator, and I really don't know why! But it can be taken as a good test for insensitivity to the "space bug".

And here is an example of reducing false positives by AV scanners. It's the file Configure PopMenu.exe: Old results uploaded by @Dave-H: Now my new results after all measures: 19 false positive messages have been reduced to a value of 10.

Hello to all again! The work is almost done. I tested deeply my program package, and what can I say? It's working perfectly without any issues as far as I can see. False positive reports by the etablished and well-known AV scanners have been reduced. I am thrilled! Currently, I am updating the documentation in regards to the changelog. And, there were a lot of changes! And now, a special information to my core beta testers, @Dave-H, @mina7601, and @NotHereToPlayGames! When my package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 has been released, download it and, please, remove the old installation completely! Do all from scratch! Due to the changes, a simple replacing of files is neither good nor recommended. It could lead to error messages. Too much changes have been done! Furthermore, Microsoft .NET Framework 4.0 is now needed to run my program package. And now the most important thing! I think the release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 will be tomorrow. Cheers, AstroSkipper

I do hope so, too! Unfortunately, it's a lot of work. Changing code leads to the need of changing other code, and so on. I modified and cleaned up nearly all self-created programs. And I found bugs which apparently did not occur during the beta test.

Hello to all! Although my program package eventually passed the beta test, I still had to make significant changes due to false positives of several AV scanners: All unnecessarily embedded files have been removed from my self-created executables. Changes in calling up other programs. In all my affected programs, protection against code injection has been improved. This leads to preventing of future "space bugs", too! Different issues which could have been noticed only in very rare cases, have been fixed. All unnecessary code has been removed. New bugs I additionally found have been fixed. Autostart entries of PopMenu and the new Min2Tray, automatically added to the registry by my configuration program, have been fixed in regards to the "space bug". All message windows of my programs have been resized and adjusted for a better visibility. All my self-created program files have been recompiled by using a different compiler. All these measures have led to a reduction in the number of false positives reported by AV scanners. Now I am testing deeply my program package from scratch. Cheers, AstroSkipper

Hello @George King! That was the very first action I did! I removed unnecessarily embedded files from all self-created programs. But anyway, thanks for the hint!

I totally agree! All files self-compiled from batch sources are considered to be intrinsically vulnerable by AV scanners. Of course! But these files aren't more or less liked by AV scanners than my other ones. Hope dies last!