Post Reply 
prox-config-sidki_2019-01-26b1
Feb. 19, 2022, 02:40 AM
Post: #91
RE: prox-config-sidki_2019-01-26b1
(Feb. 18, 2022 03:43 AM)ProxRocks Wrote:  Yep, had to solve the captcha (twice).
...
Yes. Only in the CloudfairTest.cfg (as I cannot load raybuck.com in anything but it).

So now I'm pretty sure there should be a way fix 2019-01-26b1. What is it and why don't I need it...
Add Thank You Quote this message in a reply
Feb. 19, 2022, 03:48 AM
Post: #92
RE: prox-config-sidki_2019-01-26b1
(Feb. 18, 2022 02:21 PM)ProxRocks Wrote:  Hope I'm not asking too many questions.

As long as you don't mind all the rust that I have collected. Wink
I'm afraid my answers won't be as good or quick as they were back then.


(Feb. 18, 2022 02:21 PM)ProxRocks Wrote:  This one should be easy.

HaHa Smile!

(Feb. 18, 2022 02:21 PM)ProxRocks Wrote:  But how do I have it add to any of the "Display Information" flyovers that are displayed in the lower left corner?

Code:
Name = "Nullify Idle    22.02.18 [pfr] [add++]"
Active = TRUE
URL = "$TYPE(js)"
Limit = 4
Match = "Idle"
Replace = "null"

So you want notification of a hit. "Display Information" are scripts (proxjs-full.js) and filters like 'Bottom Add: Final JS Code'.
You could also add css or a comment for a 'kill' and toggle it with 'Toggle Kills' or 'Toggle Comments' in the menu.

IIRC, there are smaller hammers than 'a_jsmeth' that might allow timers to button and your page to work. Open the cfg in a text editor, search for 'a_jsmeth', shows that it disables 'Block various Events' but so does 'a_event'.
You may also be able to 'protect' the pages code from the filter that you are disabling with 'a_jsmeth'. Your filter matches and puts it back in a form or manner that the other filter doesn't match.
Or fix the error that the filter is creating with its replacement code.
Add Thank You Quote this message in a reply
Feb. 19, 2022, 03:59 AM
Post: #93
RE: prox-config-sidki_2019-01-26b1
(Feb. 19, 2022 01:24 AM)ProxRocks Wrote:  JJoe - what are your Exceptions-U entries for Google?

I'm unable to get Google Sheets / Docs / Voice / Gmail / Drive to log in while using Proxomitron.

If I had a google account, google's phone number requirement locked me out years ago.
Add Thank You Quote this message in a reply
Feb. 19, 2022, 12:07 PM
Post: #94
RE: prox-config-sidki_2019-01-26b1
(Feb. 19, 2022 03:59 AM)JJoe Wrote:  If I had a google account, google's phone number requirement locked me out years ago.

I was afraid of that Sad

But there is something seriously wrong with Proxomitron and Google and with Google's dominance, I really think a fix can/should be found. Fingers crossed.

Try this: go to any Google service sign in page but don't enter any username/password.

Instead, access the lower right Prox Menu and select bypass. A new tab will open but Proxomitron is NOT bypassed.

Could that be leading us to something as to why Google will not work ???
Add Thank You Quote this message in a reply
Feb. 19, 2022, 05:32 PM
Post: #95
RE: prox-config-sidki_2019-01-26b1
(Feb. 19, 2022 12:07 PM)ProxRocks Wrote:  Try this: go to any Google service sign in page but don't enter any username/password.

Instead, access the lower right Prox Menu and select bypass. A new tab will open but Proxomitron is NOT bypassed.

Could that be leading us to something as to why Google will not work ???

Possibly but probably not.
Google is answering our menu request with a 302 redirect to another address. This causes the bypass instruction to be lost.

We request
https://accounts.google.com/signin/v2/identifier?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin?prx-command=bypass..

Google redirects the browser to
https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin
and then they manipulate the address bar to hide the current address.

Try this address

https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin?prx-command=bypass..

Page should be bypassed and address bar will not be right.


For your other problem
The 'Timers to Button' filter is

Code:
[Patterns]
Name = "Unrequested Timers to Button     07.09.05 (fail) [sd] (d.1 l.3)"
Active = TRUE
URL = "$TST(hCT=*html)$TST(keyword=(^*.(a_js|a_jsmeth|i_timer:0|i_level:[12]).)(*.i_timer:(2$SET(0=8)|3$SET(0=4)).|$SET(0=4+8))*)$SET(jsVarsB=$TST(jsVarsB=(*$stopMe: )\1(0|$SET(3=+)([^,]+)\2) \4)\1\2\3\0\4)PrxFail$TST()"
Limit = 1
Match = "$STOP(This filter isn't supposed to get that far)"

If you were to remove 'a_jsmeth|' , having 'a_jsmeth' in your lists would not affect 'Unrequested Timers to Button'. You would still be able to allow timers with 'i_timer:0', 'i_level:1', and ' i_level:2'
.
Add Thank You Quote this message in a reply
Feb. 19, 2022, 06:46 PM (This post was last modified: Feb. 19, 2022 06:47 PM by ProxRocks.)
Post: #96
RE: prox-config-sidki_2019-01-26b1
(Feb. 19, 2022 05:32 PM)JJoe Wrote:  Google is answering our menu request with a 302 redirect to another address. This causes the bypass instruction to be lost.

We request
https://accounts.google.com/signin/v2/identifier?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin?prx-command=bypass..

Google redirects the browser to
https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin
and then they manipulate the address bar to hide the current address.

Good catch! I saw the 302 but didn't see the bold differences until you pointed them out. Thanks!


(Feb. 19, 2022 05:32 PM)JJoe Wrote:  Try this address

https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin?prx-command=bypass..

Page should be bypassed and address bar will not be right.

That works!


(Feb. 19, 2022 05:32 PM)JJoe Wrote:  For your other problem
The 'Timers to Button' filter is

Code:
[Patterns]
Name = "Unrequested Timers to Button     07.09.05 (fail) [sd] (d.1 l.3)"
Active = TRUE
URL = "$TST(hCT=*html)$TST(keyword=(^*.(a_js|a_jsmeth|i_timer:0|i_level:[12]).)(*.i_timer:(2$SET(0=8)|3$SET(0=4)).|$SET(0=4+8))*)$SET(jsVarsB=$TST(jsVarsB=(*$stopMe: )\1(0|$SET(3=+)([^,]+)\2) \4)\1\2\3\0\4)PrxFail$TST()"
Limit = 1
Match = "$STOP(This filter isn't supposed to get that far)"

If you were to remove 'a_jsmeth|' , having 'a_jsmeth' in your lists would not affect 'Unrequested Timers to Button'. You would still be able to allow timers with 'i_timer:0', 'i_level:1', and ' i_level:2'
.

Thanks, will dig a little deeper.
Add Thank You Quote this message in a reply
Feb. 26, 2022, 08:41 PM (This post was last modified: Feb. 27, 2022 12:09 AM by ProxRocks.)
Post: #97
RE: prox-config-sidki_2019-01-26b1
Is there an easy header filter to block any-and-all incoming fonts?
Or perhaps only third-party fonts fetched from domains different from the current URL?
Preferrably even block the connection to the server hosting the incoming fonts?
Add Thank You Quote this message in a reply
Feb. 27, 2022, 02:39 AM
Post: #98
RE: prox-config-sidki_2019-01-26b1
(Feb. 26, 2022 08:41 PM)ProxRocks Wrote:  Is there an easy header filter to block any-and-all incoming fonts?
...
Preferrably even block the connection to the server hosting the incoming fonts?

Not easy to block them all and block the connection.
With header filters you probably target the file extensions of the requests and then the content-type of the response.

Pick one. They do the same thing. Neither will catch all unless you are willing to accept collateral damage. For the sidki set only as these both depend on uExt variable.

Code:
[HTTP headers]
In = FALSE
Out = FALSE
Key = "! |||||||||||| 2.2 Block fonts by extension     22.02.27 (o.0) (Out)`"
URL = "$TST(uExt=eot|otf|ttf|woff?+) $SET(keyword=i_proxy:0.)$RDIR(http://127.0.0.1:8080/killed.html?$DTM(c):\u)"

In = FALSE
Out = FALSE
Key = "! |||||||||||| 2.2 Block fonts by extension \k    22.02.27 (o.0) (Out)`"
URL = "$TST(uExt=eot|otf|ttf|woff?+)"
Replace = "\k$LOG(wBlocked $GET(uExt) $DTM(c):\u)"

For the missed requests, a filter to target the content type of the response. This isn't difficult but needs some research to find all the mime types and create the matching routine.

Code:
[HTTP headers]
In = TRUE
Out = FALSE
Key = "Content-Type: Block fonts \k     22.02.27 (o.0) (In)`"
Match = "application/font-woff2"
Replace = "\k"

You could just add a bunch of 'OR' statements, "|font2|font3|etc...", as you find more.

(Feb. 26, 2022 08:41 PM)ProxRocks Wrote:  Or perhaps only third-party fonts fetched from domains different from the current URL?

Perhaps the routine in

Code:
[HTTP headers]
In = FALSE
Out = FALSE
Key = "Content-Type: 6c Log Third Party Scripts     10.10.16 [sd] (o.1 l.4) (In)"
URL = "$TST(keyword=*.i_level:[45].*)"
Match = "(text/(javascript|vbscript)|application/x-javascript)$TST(hOrigRef=(^(*:)+{1}//([^/]++.|)$TST(uDom)(^.))(\0))&\1&$LOG(RRESP $DTM(c) : Third Party Script: $GET(uFile).$GET(uExt))($TST(volat=*.log:[12]*)$ADDLST(Log-Rare,HDR_In CT_3rdP_js\t\u Ref: \0)|)"
Replace = "\1"

but some files may just look like 'third' party.
Add Thank You Quote this message in a reply
Feb. 27, 2022, 03:04 AM
Post: #99
RE: prox-config-sidki_2019-01-26b1
Thanks Thumbs Up
Add Thank You Quote this message in a reply
Feb. 27, 2022, 03:26 AM
Post: #100
RE: prox-config-sidki_2019-01-26b1
(Feb. 27, 2022 02:39 AM)JJoe Wrote:  
(Feb. 26, 2022 08:41 PM)ProxRocks Wrote:  Or perhaps only third-party fonts fetched from domains different from the current URL?
Perhaps the routine in

What about via https://developer.mozilla.org/en-US/docs...y/font-src ?
Add Thank You Quote this message in a reply
Feb. 27, 2022, 04:53 AM (This post was last modified: Feb. 27, 2022 04:58 AM by JJoe.)
Post: #101
RE: prox-config-sidki_2019-01-26b1
(Feb. 27, 2022 03:26 AM)whenever Wrote:  
(Feb. 27, 2022 02:39 AM)JJoe Wrote:  
(Feb. 26, 2022 08:41 PM)ProxRocks Wrote:  Or perhaps only third-party fonts fetched from domains different from the current URL?
Perhaps the routine in

What about via https://developer.mozilla.org/en-US/docs...y/font-src ?

Thanks. I forgot about that even though I am using it to block media. Should be easy to adapt...

Code:
[HTTP headers]
In = TRUE
Out = FALSE
Key = "Content-Security-Policy: z block fonts 22.02.27    [whenever,jjoe] (o.0) (In) `"
URL = "$TST(uProt=https:)"
Match = "\1(font-src )\2[^;]+;$SET(3=https://local.ptron:8443;)\4| (^?)$SET(1=font-src https://local.ptron:8443;)|\2$SET(1=font-src https://local.ptron:8443; )|add test"
Replace = "\1\2\3\4"

In = TRUE
Out = FALSE
Key = "Content-Security-Policy: z block media 22.01.31    [jjoe] (o.0) (In) `"
URL = "$TST(uProt=https:)"
Match = "\1(media-src 'none')\2\3| (^?)$SET(1=media-src 'none')|\2$SET(1=media-src 'none'; )|add test"
Replace = "\1\2\3"

Still working on a Content-Security-Policy routine.
"add test" is a note to remind me to add a keyword.
Needs work, if only third party blocking is desired.
Add Thank You Quote this message in a reply
Feb. 27, 2022, 04:59 AM (This post was last modified: Feb. 27, 2022 05:00 AM by ProxRocks.)
Post: #102
RE: prox-config-sidki_2019-01-26b1
I can get those filters to block almost all problematic fonts.

But not the "alegreya" font used at this site -- https://off-guardian.org/2021/09/22/30-f...cribsheet/

edit: posted while you were posting the updated filters so this comment does not apply to the post directly above
Add Thank You Quote this message in a reply
Feb. 27, 2022, 05:12 AM
Post: #103
RE: prox-config-sidki_2019-01-26b1
The Content-Security-Policy: z block fonts 22.02.27 [whenever,jjoe] (o.0) (In) filter is perfect! Thanks!
Add Thank You Quote this message in a reply
Feb. 27, 2022, 05:41 AM
Post: #104
RE: prox-config-sidki_2019-01-26b1
And many thanks for the Content-Security-Policy: z block media 22.01.31 [jjoe] (o.0) (In) filter.

Blocks a ton of annoying little "mini-video loops" on news and sports sites. Very nice!
Add Thank You Quote this message in a reply
Sep. 28, 2022, 06:06 PM (This post was last modified: Sep. 28, 2022 06:12 PM by Anno Domini.)
Post: #105
RE: prox-config-sidki_2019-01-26b1
....I'm not sure if this is the section to ask this, but when I use Google search, some of the features no longer work, unless I put Proxo in bypass. For example, 'Google reviews' for a business, Google Calculator, 'People also ask' under your Google search, and Google's stock charts no longer work (the 1D, 5D, YTD, 5Y, etc) when I click them, unless I clear my cache, put Proxo in bypass, and reload my broweser. Here are two specific links below. Can anything be done to get these working again with Proxo and the prox-config-sidki_2019-01-26b1 ? Thank you for any help !

https://www.google.com/search?q=CALCULATOR

https://www.google.com/search?client=fir...q=%24googl
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: