Products > Networking & Wireless

Being blocked suddenly from uncert'd https sites.

<< < (5/6) > >>

SiliconWizard:

--- Quote from: janoc on December 23, 2021, 09:01:21 am ---
--- Quote from: SiliconWizard on December 22, 2021, 05:31:30 pm ---Yeah, Firefox now prevents from downloading anything if the link is not https (but you can still bypass it.) Whatever it is. Like PDF files.
Fun thing is, many sites all over the world still contain many links that are not https. Including Wikipedia. If, instead of a warning that you can bypass, suddenly all access to non-https stuff was blocked, you'd break probably 90% of the web.

--- End quote ---

That's not quite true unless you turn on a non-default setting "Https only mode".

--- End quote ---

No no. That's not it. And I didn't enable anything like this lately. It just appeared in the latest Firefox version (95) as far as I've noticed, and the actual reason is there:
https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox

So it's not just non-https links, but non-https links on https pages: "mixed content", as they call it. I had to dig a little deeper to get to this.
But mixed content is extremely common.

PKTKS:

--- Quote from: peteb2 on December 21, 2021, 09:16:50 am ---This is ridiculous in my eyes. Suddenly i can't even get to this website thanks to the employer's new Security deployed by the muppets of the IT dept. ...

--- End quote ---


Answered that on another post few seconds ago..

Pissed ?  Instal a socks gateway system wide..

https://www.inet.no/dante/
http://ftp.de.debian.org/debian/pool/main/t/tsocks/


tell them to fuck off from your life..

Enough having goo and fecybu  monitoring our lives..

fuck them off
Paul

janoc:

--- Quote from: SiliconWizard on December 23, 2021, 05:45:42 pm ---
No no. That's not it. And I didn't enable anything like this lately. It just appeared in the latest Firefox version (95) as far as I've noticed, and the actual reason is there:
https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox

So it's not just non-https links, but non-https links on https pages: "mixed content", as they call it. I had to dig a little deeper to get to this.
But mixed content is extremely common.

--- End quote ---

That would not prevent you from actually visiting a non-https website. That blocking only affects e.g. scripts or images that are loaded into a secure (https) site using non-secure (unecrypted, http) sources (a poor practice). So at best your website would have some broken content (typically ads).

It has also nothing to do with links but content that is loaded automatically - i.e. not stuff that you must click on to load - images, scripts, AJAX requests, CSS styles, etc. You can still visit even a http site linked from a https one without issue.

janoc:

--- Quote from: PKTKS on December 24, 2021, 11:28:02 am ---
--- Quote from: peteb2 on December 21, 2021, 09:16:50 am ---This is ridiculous in my eyes. Suddenly i can't even get to this website thanks to the employer's new Security deployed by the muppets of the IT dept. ...

--- End quote ---


Answered that on another post few seconds ago..

Pissed ?  Instal a socks gateway system wide..


--- End quote ---

At work, on employer's equipment. Yeah right, what a good idea! (assuming you even have the necessary privileges to begin with).



--- Quote from: PKTKS on December 24, 2021, 11:28:02 am ---
tell them to fuck off from your life..

Enough having goo and fecybu  monitoring our lives..

fuck them off
Paul


--- End quote ---

I guess you don't need a job, do you?

PKTKS:

--- Quote from: janoc on December 24, 2021, 03:35:41 pm ---
At work, on employer's equipment. Yeah right, what a good idea! (assuming you even have the necessary privileges to begin with).


--- End quote ---

There are at least a half dozen ways to do that ...
You do not need specifically to "use" the corp. equipo..

As long as you have access to an account and can route traffic..

You just payload (tunnel) your socks gateway over it..

No big deal
Paul

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version