Advanced Plus Security Lenny's 2021 intention: keep this setup for a year :-)

[Lenny_Fox]

@Jan Willy

So because steel melts you can use it for a cheese-fondue?, Please do a field test, which uses the mechanism mentioned (blocking javascript in the browser)

Block first prty javascript in your Chromium based browser for nos.nl (add [*.]nos.nl) visit NOS.nl and you will see the Javascript blocked in the taskbar

Next block thord-party javascript for bbc.co.uk (ad [*.]bbc.co.uk) and visit bbc.com, you will NOT see the javascript blocked in the taskbar

Now disable third-party scripts for bbc.co.uk in uBlockOrigin and revisit bbc.com, you will see that the site is broken.

Conclusion: when you set a block javascript site permission for a website in your browser it only works for first-party scripts.

 

[Jan Willy]

@Jan Willy

So because steel melts you can use it for a cheese-fondue?, Please do a field test, which uses the mechanism mentioned (blocking javascript in the browser)

Block first prty javascript in your Chromium based browser for nos.nl (add [*.]nos.nl) visit NOS.nl and you will see the Javascript blocked in the taskbar

Next block thord-party javascript for bbc.co.uk (ad [*.]bbc.co.uk) and visit bbc.com, you will NOT see the javascript blocked in the taskbar

Now disable third-party scripts for bbc.co.uk in uBlockOrigin and revisit bbc.com, you will see that the site is broken.

Conclusion: when you set a block javascript site permission for a website in your browser it only works for first-party scripts.

We were talking about HTTP-content in HTTPS-sites. I haven't seen such elements in your examples. So we shouldn't mix apples and oranges. Based on the testsite I referred to in my earlier post, I may assume that MS Edge at default does the right thing. It blocks HTTP-content in HTTPS-sites regardless of the type of content.

Edit: Look at Site Permissions.

 

[Lenny_Fox]

We were talking about HTTP-content in HTTPS-sites. I haven't seen such elements in your examples. So we shouldn't mix apples and oranges. Based on the testside I referred to in my earlier post, I may assume that MS Edge at default does the right thing. It blocks HTTP-content in HTTPS-sites regardless of the type of content.

Edit: Look at Site Permissions.

View attachment 257331

Just do the test I explained. It proofs that first party content is blocked, not third-party

 

[Jan Willy]

Just do the test I explained. It proofs that first party content is blocked, not third-party

I said before: we shouldn't mix apples and oranges. So let's end this discussion.

 

[ForgottenSeer 85179]

This only blocks first party scripts. When you are on a HTTPS website which uses HTTP scripts as third-party those insecure scripts will be executed. The HTTP://* rule in blocking scripts does not protect you against that.

Are you sure? Edge should display an info in URL bar in that case because of "insecure content". This can be configured in Edge permissions.

I don't get your responses. Frst you are posting that blocking third-party scipts hardly has any advantage, now you are advising to block all http-scripts.

Crippling websites isn't recommended. But blocking insecure HTTP scripts (websites still *works* without scripts) is best practice.
Anyway, for normal user's this doesn't matter much.

Are you just responding to have a discussion/making fun? I dont understand why you are posting wrong information.

Don't know what you mean but if you want, i can stop posting here.

 

[Lenny_Fox]

Are you sure? Edge should display an info in URL bar in that case because of "insecure content". This can be configured in Edge permissions.


Crippling websites isn't recommended. But blocking insecure HTTP scripts (websites still *works* without scripts) is best practice.
Anyway, for normal user's this doesn't matter much.


Don't know what you mean but if you want, i can stop posting here.

As with @JanWilly lets agree to disagree (and you are free to post anywhere like all other members)

 

[Lenny_Fox]

After finding out my CPU was to old for Windows11, I played with some sandbox programs (Comodo, ReHips and Sandboxie). Settled for Sandboxie to secure my privacy hardened firefox (which I use as secondary browser).

 

[ErzCrz]

After finding out my CPU was to old for Windows11, I played with some sandbox programs (Comodo, ReHips and Sandboxie). Settled for Sandboxie to secure my privacy hardened firefox (which I use as secondary browser).

I can't be certain that mine is new enough either with an i3-4005U but I've got 12 gig ram. The compatabiliy tool is mean to be relaunched soon which will make that more straight forward. We'll just have to wait and see I guess...