Comment

Comment on Is HTTPS a scam?

<- View Parent

Dr_Satan@lemm.ee ⁨4⁩ ⁨months⁩ ago

Yes, security. We love security now. The argument is well known.

But now you need permission from an official to have a web site. That’s bad, right?

source

Sort:hotnew top

fubo@lemmy.world ⁨4⁩ ⁨months⁩ ago
You should probably be more concerned about DNS than HTTPS. DNS is a point where government censors actually do go after web sites they don’t like.

source
adespoton@lemmy.ca ⁨4⁩ ⁨months⁩ ago
What? I’ve got all sorts of self hosted websites. Encrypted by HTTPS. No permission needed. If Let’s Encrypt vanished, I’d just switch to self-signing my certificates and using a pinning service.

source
- Dr_Satan@lemm.ee ⁨4⁩ ⁨months⁩ ago
  Doesn’t chrome flag self-signed certificates?
  
  Ok, I didn’t know that was a thing. Thanks
  
  source
rdyoung@lemmy.world ⁨4⁩ ⁨months⁩ ago
Wait, what? Who needs permission from whom to run a website? I can spin up a website right now, I can spin up as many as I want. You can too. There is no permission needed to get https setup on your website, it can be simple or a bit more involved depending on who you are using as your host or if you are handling everything yourself from a vps or locally hosted server.

Please do yourself a favor and delete this thread and stop commenting. You are way out your depths here and have no idea how anything works.

source
toasteecup@lemmy.world ⁨4⁩ ⁨months⁩ ago
I don’t need permission to have a website. I need to prove I have control over a domain so that I can get a certificate for it. That way I can’t get a certificate for lemmy.org when I don’t own or control lemmy.org.

I don’t know what drug You’re smoking friend but please stop. It’s giving you brainrot.

source
Nyfure@kbin.social ⁨4⁩ ⁨months⁩ ago
Yes, you need an organization which signs your certificate, so it is trusted by default. This is our trust-anchor so we know the certificate presented was validated and is was given only to the website owner.
There are numerous around the world for that.
And if that is no longer offered, you can just not have your certificate signed, which means browsers will complain about it.
But you can trust your own certificate yourself. Or create your own certificate authority which can then give our certificates for the community to trust as their new trust anchor.

You can even not have certificates, but keep an weak form of TLS (no idea if browsers support TLS_DH_anon_*), but its still encrypted and can only be broken by an active Man-in-the-Middle-attack. (which is theoretically detectable later on)
Diffie-Hellman is an awesome key-exchange.

source