Hacker News new | ask | show | jobs
by 1vuio0pswjnm7 955 days ago
Maybe it's more than security theater. With mandatory TLS, i.e., encryption plus third party-mediated authentication, the ability to publish a website comes under the control of third parties, so-called "Certificate Authorities" (CAs).

The source of this third party "authority" is unclear. If a CA uses DNS for verification, then the "authority" is ultimately ICANN. And we know that ICANN's "authority" is completely faked up. It has no legal basis. These pseudo regulatory bodies have no democratic process to ensure they represent www users paying for internet subscriptions. As it happens, these organisations generally answer only to so-called "tech" companies.

Effectively, CAs and browser vendors end up gatekeeping who can have a website on the public internet and who cannot. Not to mention who can be an "authority" for what is a trustowrthy website and what is not (CA/Browser Forum).

The hoops that the browser vendors make a www user jump through in order to trust a website without the assistance of a third party are substantial and unreasonable. It seems that no www user can be expected to make their own decisions about what they trust and what they don't. The decision is pre-made, certificates are pre-installed, autonomy is pre-sacrificed, delegated to so-called "tech" companies.

Meanwhile these so-called "tech" companies, who are also the browser vendors, are commercial entities engaged in data collection for online advertising purposes. For more informed users, these actors are perhaps the greatest eavesdropping threat that they face. The largest and most influential of them has been sued for wiretapping www users on multiple occassions.

There are conflict of interest issues all over the place.

tl;dr Even if the contents of the transmission are not sensitive and perfectly suited to plain text, the system put in place by so-called "tech" companies, to benefit themselves at the expense of every www users' privacy, ensures that TLS must be used as a means of identifying what is an "acceptable" website and what is not. Absence of a certificate from a self-appointed, third party certificate authority means "not acceptable". Presence of certificates from first party authorities, i.e., ordinary www users, means "not acceptable".

3 comments

Let's encrypt is doing god's[1] work to work around the CA scam. And they've made it extremely easy to use. Literally just run one command and you have SSL on your website. May take a few more commands if you're not using one of the more standard HTTP servers.

You have to have a domain to use it obviously. Lucky there are other god's workers like duckdns to work around the domain scam too.

https://letsencrypt.org/ https://www.duckdns.org/

[1] Obviously not referring to any theistic entity here, but more to something like the spirit of FSF or whathaveyou.

absolutely nothing prevents you from either:

- adding another root CA, or

- bypassing HTTPS warnings, or

- taking 10 minutes to set up LetsEncrypt

and for obvious reasons, neither of the first two should be easy