![]() |
|
Proxomitron Reborn - Printable Version +- The Un-Official Proxomitron Forum (https://www.prxbx.com/forums) +-- Forum: Forum Related (/forumdisplay.php?fid=37) +--- Forum: Proxomitron Program (/forumdisplay.php?fid=4) +--- Thread: Proxomitron Reborn (/showthread.php?tid=2331) |
RE: Proxomitron Reborn - ProxRocks - Apr. 09, 2024 08:06 PM Is all of this supposed to clear this browser warning? RE: Proxomitron Reborn - JJoe - Apr. 10, 2024 01:55 AM That may depend upon the browser and the reason for the warning. I would expect the files that these are replacing to prevent that warning. My guess is you missed a step or more in setting up Reborn for https. Which browser and can you share the details of its warning? (Apr. 09, 2024 08:06 PM)ProxRocks Wrote: Is all of this supposed to clear this browser warning? RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 09:09 AM I get that warning in *EVERY* Chrome-based browser I've ever used with Proxomitron. I currently use Ungoogled Chromium v114 (I have no use for "newer" versions). What are all of the "steps" and I'll double-check them one-by-one? RE: Proxomitron Reborn - JJoe - Apr. 10, 2024 04:27 PM I think your cert has been deprecated. I'll look at 'Ungoogled Chromium v114' when I get a chance. Start with the attached files. (Apr. 10, 2024 09:09 AM)ProxRocks Wrote: I get that warning in *EVERY* Chrome-based browser I've ever used with Proxomitron. [attachment=1168] ReadMe.txt Wrote:Add files to the Proxomitron exe's directory. Edit: Corrections/Details and New files RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 07:19 PM Thanks! The "ProxomitronSSLFilteringRootCA.crt" import fixed it! Next question - How was this file created in case I ever need to "roll my own" (as sidki used to call it)? RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 07:24 PM (Apr. 09, 2024 12:35 PM)JJoe Wrote:(Apr. 02, 2024 05:09 AM)amy Wrote: Happy Easter! Proxomitron Reborn 4.7.0.0 has been released! I'm assuming that the libcrypto-3.dll and libssl-3.dll files just sit in the main folder alongside the Proxo/Proxomitron .exe? How does one "test" if the .dll's are being used or not? RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 07:48 PM (Apr. 10, 2024 07:19 PM)ProxRocks Wrote: How was this file created in case I ever need to "roll my own" (as sidki used to call it)? Disregard, I forgot about the Reborn built-in cert generator. I've tried it in the past and it did not work. I will need to experiment with the settings/options as I've always just used the "default". The "default" generated a cert that did not work. I'll experiment. RE: Proxomitron Reborn - JJoe - Apr. 10, 2024 08:34 PM Use Reborn's certificate generator (Main dialog>>Config>>HTTPS) to generate "proxcert.pem" and "proxcert_certonly.pem". Use Firefox, OpenSSL, or other to convert "proxcert_certonly.pem" to "ProxomitronSSLFilteringRootCA.crt." (Apr. 10, 2024 07:19 PM)ProxRocks Wrote: Next question - How was this file created in case I ever need to "roll my own" (as sidki used to call it)? Edit: Corrections/Details RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 09:08 PM Here is an easy test. All you have to do is load this .png and it will tell you if you are TLS 1.2 or TLS 1.3. https://check-tls.akamai.io/v1/tlsv.png RE: Proxomitron Reborn - ProxRocks - Apr. 10, 2024 09:19 PM I'm still missing something. I cannot get TLS 1.3 when running through Proxo Reborn. RE: Proxomitron Reborn - JJoe - Apr. 11, 2024 12:45 AM Yes, the libcrypto-3.dll and libssl-3.dll files just sit in the main folder with the new exe. If you have not, remove or rename the old DLLs, libeay32 and ssleay32. Start Reborn with a cfg that uses SSLeay/OpenSSL, (Main dialog>>Config>>HTTP). A little awkward to mention but I may have made this kind of mistake more than I will admit... Make sure that the new exe is the one being tested. ![]() To test functionality, you can use an online service like https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html. The Proxomitron's Log Window may indicate TLS 1.3. Log Window Wrote:+++SSL:GET 2142+++ (Apr. 10, 2024 07:24 PM)ProxRocks Wrote: ... (Apr. 10, 2024 09:19 PM)ProxRocks Wrote: I'm still missing something. RE: Proxomitron Reborn - amy - Apr. 11, 2024 01:38 AM Also, you can visit http://local.ptron/.pinfo/ssl/ to see some more info on your SSL configuration, including the currently loaded OpenSSL version. RE: Proxomitron Reborn - ProxRocks - Apr. 11, 2024 07:26 AM Okay, I got TLS 1.3 working. I had two issues. First, I was using all four .dll's instead of just the two new .dll's. Second, I was applying PtronGUI_4.6.0.5(h).exe to Reborn_4700R. Looks like I will have to modify the GUI manually instead. RE: Proxomitron Reborn - ProxRocks - Apr. 12, 2024 09:13 AM Running the newest Reborn has become a slight nightmare on my system. I am getting the below error SEVERAL times throughout a browsing session. Is anybody else? I'm on Win10 x64 LTSB and Ungoogled Chromium v114. RE: Proxomitron Reborn - Anno Domini - Apr. 12, 2024 09:47 PM WOW, an Easter present ! Version 4.7.0.0 ! Thank you s-o-o-o-o much Amy !!! You're a true treasure to the Proxomitron community !!! Guys, I've said this before. I operate at a 4th grade level when it comes to much of what you talk about here. I read your comments to try and install Version 4.7.0.0 correctly, and I made a short list of what I did in order. Proxomitron's Log Window now indicates TLS 1.3 and it appears to be running fine. Can anyone confirm I updated it properly ? Thank you. 1.) I downloaded ProxomitronReborn_4700R.zip containing the help folder, changes.txt, and proxo.exe. I added those three files to my Proxomitron folder replacing the old ones. 2.) I deleted the old DLLs -- libeay32 and ssleay32 in my Proxomitron folder-- and then added libcrypto-3.dll and libssl-3.dll files in there 3.) I started Proxomitron and generated a new proxcert.pem and exited Proxomitron. 4.) I started my browser, deleted my old Proxomitron certificate, and then added proxcert_certonly.pem to browser's certificate store. 5.) Started Proxomitron, went online, and it works. Proxomitron's Log Window now indicates TLS 1.3. |