Let's Encrypt issues 35 certs every second
twitter.com
Let's Encrypt issues 35 certs every second
1–10 of 31 posts
Re: Let's Encrypt issues 35 certs every second
#2Let's Encrypt has definitely been a net positive to the internet as a whole. I do wish more services/tools had cleaner integration. I've switched to mostly using Caddy for personal web and reverse proxy chores as it's just much easier to deal with imo.
Re: Let's Encrypt issues 35 certs every second
#3And somehow having one of these prevents your website from being "illegitimate"...
Re: Let's Encrypt issues 35 certs every second
#4And somehow having one of these prevents your website from being "illegitimate"...
It prevents the data between you and the requester from being read or tampered with in-transit.
Before HTTPS was popular, I used to see ISPs inject tracking JavaScript or ads into arbitrary websites for their "customers".
So, in some sense yes, this preserves a legitimate version of your website for the requester.
Re: Let's Encrypt issues 35 certs every second
#5And somehow having one of these prevents your website from being "illegitimate"...
Do you have a specific problem with the dns01 or http01 challenges used to validate a domain before issuing a certificate?
Or are you just being snarky for the sake of being snarky?
Re: Let's Encrypt issues 35 certs every second
#6Let's Encrypt has definitely been a net positive to the internet as a whole. I do wish more services/tools had cleaner integration. I've switched to mostly using Caddy for personal web and reverse proxy chores as it's just much easier to deal with imo.
Caddy ist just awesome. I regularly wonder why most online tutorials don't use it. Because it just works and is so much easier to work with than all the alternatives.
Re: Let's Encrypt issues 35 certs every second
#7And somehow having one of these prevents your website from being "illegitimate"...
It doesn't, no. Whoever told you that is wrong.
Bad actors can get TLS certificates issued for their phishing sites just the same as you can for a regular website. Encryption is for everybody.
Re: Let's Encrypt issues 35 certs every second
#8And somehow having one of these prevents your website from being "illegitimate"...
It prevents the data between you and the requester from being read or tampered with in-transit. Before HTTPS was popular, I used to see ISPs inject tracking JavaScript or ads into arbitrary websites for their "customers". So, in some sense yes, this preserves a legitimate version of your website for the requester.
And browsers would give a huge red alert for self-signed certs but say nothing about plaintext HTTP. Presumably that’s where the snark is coming from. Clearly the plaintext HTTP was less secure than self-signed certs but browsers perpetuated the “trusted” cert cartel.
Re: Let's Encrypt issues 35 certs every second
#9Earlier quoted context omitted.
It prevents the data between you and the requester from being read or tampered with in-transit. Before HTTPS was popular, I used to see ISPs inject tracking JavaScript or ads into arbitrary websites for their "customers". So, in some sense yes, this preserves a legitimate version of your website for the requester.
And browsers would give a huge red alert for self-signed certs but say nothing about plaintext HTTP. Presumably that’s where the snark is coming from. Clearly the plaintext HTTP was less secure than self-signed certs but browsers perpetuated the “trusted” cert cartel.
Having a certificate from a CA like LE proves that you don't have a local MITM. The MITM would have to also somehow get between LE's servers and the website in order to get a trusted certificate. A self-signed certificate does not have that guarantee.
Re: Let's Encrypt issues 35 certs every second
#10As someone who is really tried of going through the small pain to pull a new cert every 3 months and then apply it to multiple machines.. what's the norm place for just buying a 1 or 2 year certificate? and is it pretty cheap?