Browsers not using http doen't bother me much. You don't have to use an up-to-date browser. You don't even have to use a graphical one. Lynx is
100% free of all javascript exploits because it doesn't use Javascript.
My worry comes when the powers that be start forcing ISPs to monitor all traffic and disallow unapproved traffic e.g. Tor onion services or other services that are unable to be policed efficiently (usenet, irc).
HTTPS-Only mode ... will also ask for your permission beforeconnecting to a website if it doesn't support secure connections.
I give it about 3 years before all massive commercial browsers stop
allowing you to visit HTTP sites at all and Firefox only allows if you
use their unstable beta build.
HTTPS only comes from a good place. People want privacy from their governments' pervasive spying. Unfortunately, by going full retard and
not allowing HTTP combined with the centralized nature of cert
authorities, this privacy push has and will result in a situation that absolutely delights those same central governments. Because now they
will have full control of who can speak and who can not.
https://blog.mozilla.org/security/2020/11/17/firefox-83-introduces-https-only-mode/
I give it about 3 years before all massive commercial browsers stop
allowing you to visit HTTP sites at all and Firefox only allows if you
use their unstable beta build.
HTTPS only, transport layer security only (for IRC, for SMTP, for HTTP,
etc), will be the end of personal autonomy on the internet. There are
only a handful of cert authories that actually get used as as each of
those get bigger they become more easily corrupted by money and external government influence. We saw it with dot org. I doubt LetsEncrypt will
be significantly more robust over the same time scales.
HTTPS only is insidious. The very people we've come to trust are working
for our privacy are now working to solidify and centralize a system that allows for a few big players to decide on whim (or otherwise) who can
speak. And it has to stop.
And no, self-signed certs won't be the solution. Most browsers
already put up giant scaremongering warnings about self-signed certs.
It won't be too long until they're not allowed at all in the big
corporate browsers.
HTTPS only comes from a good place. People want privacy from their governments' pervasive spying. Unfortunately, by going full retard
and not allowing HTTP combined with the centralized nature of cert authorities, this privacy push has and will result in a situation
that absolutely delights those same central governments. Because now
they will have full control of who can speak and who can not.
https://blog.mozilla.org/security/2020/11/17/firefox-83-introduces-https-only-mode/
I give it about 3 years before all massive commercial browsers stop
allowing you to visit HTTP sites at all and Firefox only allows if
you use their unstable beta build.
HTTPS only, transport layer security only (for IRC, for SMTP, for
HTTP, etc), will be the end of personal autonomy on the internet.
There are only a handful of cert authories that actually get used as
as each of those get bigger they become more easily corrupted by
money and external government influence. We saw it with dot org. I
doubt LetsEncrypt will be significantly more robust over the same
time scales.
HTTPS only is insidious. The very people we've come to trust are
working for our privacy are now working to solidify and centralize a
system that allows for a few big players to decide on whim (or
otherwise) who can speak. And it has to stop.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 100:48:41 |
Calls: | 2,071 |
Calls today: | 1 |
Files: | 11,134 |
Messages: | 946,973 |