prox-config-sidki_2019-01-26b1
|
Sep. 16, 2019, 03:18 AM
Post: #16
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
(Sep. 15, 2019 02:42 AM)thypentacle Wrote: For issue 1, If you don't edit the v2 into a v3 you get several red 'insecure' results with the following two example tests:The defaults for Proxomitron Reborn are deliberately oriented towards "compatibility" rather than "security", with the overly aggressive behaviour of browsers leaning toward the latter some sites may become inaccessible, even if they were considered "insecure", and Proxomitron lets you access them agan. (Sep. 15, 2019 02:42 AM)thypentacle Wrote: I did note that pushing the 'abort' button can crash the app sometimes tho... so maybe I broke the 'bypass' feature when I did that.That's a known bug which has been there since Scott's, is not easy to fix (which is probably why he didn't do it), and doesn't happen all the time, but is on my list of things to fix for the next release. |
|||
Sep. 16, 2019, 04:33 PM
(This post was last modified: Sep. 16, 2019 04:35 PM by JJoe.)
Post: #17
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
(Sep. 15, 2019 02:42 AM)thypentacle Wrote: For issue 2 I think I fixed that one on my end by not using Opera. I use the new Opera portable. (Sep. 15, 2019 02:42 AM)thypentacle Wrote: For issue 3 here's a few that fail loading... Ahh... Filtering will break web sites. The user is expected to add 'Exceptions' to 'Exceptions-U.ptxt' to regain desired behavior. However, I'll claim discordapp and teams.microsoft.com. Depending on which cfg you are using, 'Exceptions-U.ptxt' needs at least: Code: ##community.quirky.com/login Discordapp's Content-Security-Policy header uses nonce. Code: default-src https://local.ptron:8443 'unsafe-inline' 'self'; 'Nonce' causes the browser to ignore our 'unsafe-inline' addition and our inline scripts for discordapp.com/channels/@me. The simple choice is to bypass the affected pages or add Exceptions for the broken routines. Another is to remove "nonce' from the header. Warning: This would also allow malicious scripts without the nonce attribute to run. Code: [HTTP headers] The better (for our point of view) but more time consuming choice would be to capture the nonce and add it to our rewritten scripts. discordapp is also using the integrity attribute. Code: <script src="/assets/dea071166a0cf8791a1e.js" integrity="sha256-0kdB3V4HCTqbit21e3K2rY7ypJiNdjmjyQ9MFnPJHCI= sha512-EtY9vjf3AHCuuRqOurhkNITyJtCXmfgFQmOCD4w/LbtgvstqFufIiFfTetU24nhw+n1CD//myNXaNa59lT9EQg=="> The browser will reject the script if its hash isn't the integrity attribute's value. A filtered script's hash will not match. The simple choice is to bypass the affected resources. Warning: This would also allow malicious files to run. Code: [Patterns] more to come... |
|||
Sep. 16, 2019, 05:57 PM
(This post was last modified: Sep. 16, 2019 06:01 PM by thypentacle.)
Post: #18
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
(Sep. 16, 2019 03:18 AM)amy Wrote: The defaults for Proxomitron Reborn are deliberately oriented towards "compatibility" rather than "security", with the overly aggressive behaviour of browsers leaning toward the latter some sites may become inaccessible, even if they were considered "insecure", and Proxomitron lets you access them agan. In the case of the security check sites, they load secure... the insecurity in this case is really just their report showing the following in their scanner information display: 0xc011 TLS_ECDHE_RSA_WITH_RC4_128_SHA INSECURE: RC4, SHA-1 0xc007 TLS_ECDHE_ECDSA_WITH_RC4_128_SHA INSECURE: RC4, SHA-1 0x0005 TLS_RSA_WITH_RC4_128_SHA INSECURE: NO PFS, RC4, SHA-1 0x0004 TLS_RSA_WITH_RC4_128_MD5 INSECURE: NO PFS, RC4, MD5 ...and the other site showing the same ones to confirm. TLS_ECDHE_RSA_WITH_RC4_128_SHA (0xc011) INSECURE 128 TLS_ECDHE_ECDSA_WITH_RC4_128_SHA (0xc007) INSECURE 128 TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 The editing of the config file just prevents them from being accessible as a cipher option at all I guess. (v2 edit to v3 seems to make them no longer allowed to be used so they are not accessible to test) ? (Sep. 16, 2019 03:18 AM)amy Wrote: That's a known bug which has been there since Scott's, is not easy to fix (which is probably why he didn't do it), and doesn't happen all the time, but is on my list of things to fix for the next release. Yep I remembered after messing with it again... my solution was to remove the abort button myself back in the day so I'd simply never use it on accident. (Easy Resource Hacker solution. He also has some crooked text boxes my OCD forced me to repair as well.. even tho they are invisible.) lol If you are actually planning to fix that feature that would be awesome! Not critical of course, I can always remove the button again... and besides, the bypass seems to work fine as an alternative of sorts. (and it's easy enough to just exit the app if one feels the need to cut n run) ----------------------- (Sep. 16, 2019 04:33 PM)JJoe Wrote: I use the new Opera portable. I've had nothing but trouble since the newest Opera update. It was already giving me grief in a few ways (full install tho, not portable). This is likely a result of uBlock Origin running on it. (yes I whitelist local.ptron) Firefox handles additional addons much better than Opera seems to. I've not had the bypass button in Proxomitron break even once with Firefox like it did on the full install Opera. I may try the portable version now that you mentioned it however. (Sep. 16, 2019 04:33 PM)JJoe Wrote: Ahh... Filtering will break web sites. I've been adding in exceptions to get around all of them and it seems to work fine. I'll play around with those new filters you made. (even tho they make things unsafe it could be interesting to test) Looking forward to what more there is to come? ---------------------- Beyond replies above, I wanted to say again it's great you two are working on this. It seems like a great idea if we could maybe make the next release of Proxomitron Reborn perhaps be bundled with a new default (less strict / novice user type) filter set to get everyone going? I mean it's nice to throw in a setting that has everything plus the kitchen sink, but messing with cookies, cache, and JS too much these days essentially breaks about every large website there is that is popular. (even when I set to 'minimum' with current config, a lot is broken and requires manual repair by jumping into text files... at lowest level even my gmail login doesn't work till I manually disable one of the JS filters in the anti-scripting section) Would be nice if a default setting was a bit more user friendly. Site specific fixes are not fully practical either and having a less strict default would prevent the need. (it's too hard to keep up and update that stuff even if it's created by a company, let alone a hobby project) It may be better to just have a default stock option to allow more function and if the user wants to get 'heavy duty' they can activate the 'advanced' option in the config. (I'd also drop the proxmenu overlay... even with the most ideal config I still can't get it to show up all the time... maybe 90%.) Finally (sure yer glad to read that word) it would be very handy if a pack could be made with the latest available drivers already included. (zlib/SSL) Newest zlib I can get working is 1.2.8.1 / and newest SSL I can find is 1.0.1q. Would be even better (and safer) if it was at all possible to get the newest versions of them to work. I've tried newest 32bit builds of zlib and SSL but both fail. Just would be awesome if new people that find this great software can just download one thing and run it and be essentially done and ready to go out of the box after a simple change of their proxy settings. (with the option of course to get into more complex filtering by raising the filter level or creating their own filters) Ok nuff said. I'll shutup now. :P |
|||
Sep. 16, 2019, 06:19 PM
(This post was last modified: Sep. 16, 2019 06:43 PM by thypentacle.)
Post: #19
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
Forgot to mention... another thing you may want to either drop or only have in an advanced config, is the ad blocking. To do that well requires constant updates so as not to break websites all over the place. (see uBlock Origin and similar) You can put in a compromise in the form of simply allowing host blocking. I myself just manually add hosts to block from various text list sources and put that in one of the ptext files. The ad blocking in Proxomitron was a good idea back when the development was active... not so much these days. It's better to let ads through than to have to add website exceptions all the time and they get through anyways cause of the exception.
Most people will be running this along side a full ad blocker anyways. (and it's best not to have multiple ones going) I'd concentrate on making a default set about safety. Some ads could be blocked if they are the more 'tracking' type perhaps, but otherwise let users handle that with host/block lists additions or the use of other software. Most people are likely not going to use Proxomitron for ad blocking when the before mentioned one above and others are super popular and already available. (and receive constant updates) In fact, if you want to make even the hosts blocking easier, you could do it how uBlock does some of its stuff and link to the source block lists for Proxomitron to read and update itself with. (optional of course, some users prefer manual updates) I'll shutup for real now. lol |
|||
Oct. 10, 2019, 09:10 PM
Post: #20
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
Excellent. Quick question. Is the current download file in the OP updated with fixes or tweaks from later discussions in the thread? (I hope I hope)
Thanks, dude, you're the best. |
|||
Oct. 11, 2019, 04:21 PM
Post: #21
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1 | |||
The following 1 user says Thank You to JJoe for this post: mizzmona |
Jan. 21, 2022, 01:19 PM
Post: #22
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
Still digging through this thread but have a quick question (unsure how frequent other members still visit the forum).
Is this behavior (see attachmed) intentional? |
|||
Jan. 21, 2022, 11:48 PM
Post: #23
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1 | |||
Jan. 22, 2022, 12:20 AM
Post: #24
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
But I'm wondering why you aren't seeing
Code: https://local.ptron:8443/sidki_h_2019-01-26b1/CSS/dummy.css?join=menu,m-moz instead of Code: http://local.ptron/sidki_h_2019-01-26b1/CSS/dummy.css?join=menu,m-moz Do you have ! * Use Local.Ptron https file server ProxN46R+ (edit!) ! * Set 'localptron' variable enabled? Can you view https://local.ptron:8443/sidki_h_2019-01-26b1/CSS/dummy.css?join=menu,m-moz? |
|||
Jan. 22, 2022, 08:39 AM
Post: #25
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
(Jan. 22, 2022 12:20 AM)JJoe Wrote: Do you haveYes. 2022-01-22_3-34-22.png (Size: 10.26 KB / Downloads: 207) (Jan. 22, 2022 12:20 AM)JJoe Wrote: Can you view https://local.ptron:8443/sidki_h_2019-01-26b1/CSS/dummy.css?join=menu,m-moz?Yes. 2022-01-22_3-04-26.png (Size: 23.41 KB / Downloads: 207) |
|||
Jan. 22, 2022, 11:33 AM
Post: #26
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
Are you still using Opera Portable as reported in one of your posts?
Do you use any extensions such as NoScript or uMatrix? I use a modified Chromium-based browser called 360Chrome. It's originally Chinese, modded/repacked by Russians, then modded to English by me (and redistributed at MSFN.org). I use Tampermonkey, uMatrix, Stylus, and NoScript browser extensions. NoScript is the only issue with attempting to bring Proxomitron Reborn back into my arsenal. I can block all script via Proxomitron's "lists" but it is FAR easier to block via NoScript's GUI. So if you block scripts to MSFN.org, then you cannot allow the scripts that are loaded via Proxomitron (menu, flyover info links, etc). But if "local.ptron" is always the top domain, then I can allow Proxomitron's scripts while still blocking MSFN.org's scripts. |
|||
Jan. 22, 2022, 10:13 PM
Post: #27
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1 | |||
Jan. 23, 2022, 02:57 AM
Post: #28
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
Noted.
I kind of need a way to get Proxomitron to work "alongside" extensions such as NoScript else I doubt the MSFN Crowd will really give Proxomitron any light of day. It's generally too intimidating to those of us that haven't been using it for 18 years. |
|||
Jan. 23, 2022, 05:45 PM
Post: #29
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
When I visit http://www.google.com, I get the Proxomitron Menu in the lower right corner and the Information Hovers in the lower left corner.
But as soon as I do an actual search, I get neither. What could cause that? |
|||
Jan. 24, 2022, 04:32 AM
Post: #30
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
I don't see that exact problem with Opera but there is a problem.
Google is sending some browsers a Content-Security-Policy header that uses 'nonce' and 'strict-dynamic'. This causes the browser to ignore our 'unsafe-inline' addition and our inline scripts. Code: Content-Security-Policy: object-src 'none';base-uri 'self';script-src 'nonce-stringhere==' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/cdt1 The simple choice is to bypass or ignore the affected pages... Another is to remove 'nonce' and 'strict-dynamic' from the header. Warning: This would also allow malicious scripts, without the nonce attribute, and others to run. Code: [HTTP headers] As before, the better (for our point of view) but more time consuming choice would be to capture the nonce and add it to our rewritten scripts. (Jan. 23, 2022 05:45 PM)ProxRocks Wrote: When I visit http://www.google.com, I get the Proxomitron Menu in the lower right corner and the Information Hovers in the lower left corner. |
|||
« Next Oldest | Next Newest »
|