51–60 of 311 posts
Earlier quoted context omitted.
It's probably more attributed to browsers marking non-https as 'Not Secure' than anything but LetsEncrypt definitely has had a substantial impact to make that change possible.
> It's probably more attributed to browsers marking non-https as 'Not Secure' Browsers couldn't have done that if https wasn't free and simple for servers.
To the 90%: if you've got nothing to hide then why are you encrypting your traffic?
Earlier quoted context omitted.
Is a LetsEncrypt certificate "just as secure" as other certs? I have to imagine the answer is "no" simply because LetsEncrypt is free and the other certs aren't -- what more do you get by paying for a cert?
It is just as secure, you get nothing more by paying.
Sometimes I hear about people just looking for "SSL certificates" because somebody told them that they should have one, and search engines would lead them to those websites; probably that's how it still works.
Earlier quoted context omitted.
It is just as secure, you get nothing more by paying.
So for my personal projects, I use lets encrypt. As far as I know (and I could be wrong now, haven't checked in a while) - their certs are only good for 3 months. Which is simple enough to get around - run a script on your box that updates the cert every 90 days automatically. At work, we use a paid certificate that is good for a longer period of time (normally a year). So that's one benefit to paying, I suppose. As…
To the 90%: if you've got nothing to hide then why are you encrypting your traffic?
Probably sarcasm but...why shut the door when you're in the bathroom?
I think I first heard the analogy in Cory Doctorow's presentation The Coming Civil War over General-purpose Computing, which was ironically given at Google. I highly recommend people watch it.
Earlier quoted context omitted.
It is just as secure, you get nothing more by paying.
So for my personal projects, I use lets encrypt. As far as I know (and I could be wrong now, haven't checked in a while) - their certs are only good for 3 months. Which is simple enough to get around - run a script on your box that updates the cert every 90 days automatically. At work, we use a paid certificate that is good for a longer period of time (normally a year). So that's one benefit to paying, I suppose. As…
(It's been a bit sinse I went through it but I think it may be as simple as a extra flag in the command to generate the inital cert)
Does this include Netflix traffic? Which would skew the results.
Firefox - 80% https://letsencrypt.org/stats/
Google -- 88% on Android; 84% on Windows; 91% on Mac; 73% on Linux https://transparencyreport.google.com/https/overview?hl=en