41–50 of 311 posts
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?
It's been at over 90% for more than a month, from what I can tell
https://netmarketshare.com/report.aspx?options=%7B%22filter%...
I wonder how many fuel is burned to power servers and browsers to constantly encrypt and decrypt data which could be transferred much more efficiently unencrypted.
I bet if you stress test a server via http and via https, the CPU time won't be as different as you might think. The main efficiency lost is that you can no longer have big shared cache networks for everybody, but those were a security risk anyway.
Today, the landscape looks more like: You visit Google, click some links that open in AMP (still Google), visit some social networks (primarily Twitter and FB-owned properties). These companies already operate TLS-only, which helps these numbers.
To the 90%: if you've got nothing to hide then why are you encrypting your traffic?
Earlier quoted context omitted.
If that doesn't work, there's also the argument that "credit card providers require it, and could stop you from taking credit cards until you fix it".
You're right, but didn't have to. This guy when he could get past being mad at me knew that was against the rules. Also even if it was allowed, no one wants to shop at a place that says Not Secure. Side topic, but I've been trying to explain to our terrible CFO for years that PCI / PCI DSS is a real thing. He thinks that's the type of regulation that only giant companies have to deal with.
Also likely because in the past the internet was really diverse. One would visit 20 sites possibly during one session. Today, the landscape looks more like: You visit Google, click some links that open in AMP (still Google), visit some social networks (primarily Twitter and FB-owned properties). These companies already operate TLS-only, which helps these numbers.
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.
Pretty much this. I ran into a local store taking credit cards awhile back, no TLS, weird, so I go to the store owner in person. I explain the problem and he insists that can't be the case, he's mad at me. "See! It's got a lock on the website!"... on the homepage. I direct him to the store and now it says Not Secure. That did more to explain the situation than my attempt at TLS and HTTPS and Certs. He was able to cal…
Earlier quoted context omitted.
Pretty much this. I ran into a local store taking credit cards awhile back, no TLS, weird, so I go to the store owner in person. I explain the problem and he insists that can't be the case, he's mad at me. "See! It's got a lock on the website!"... on the homepage. I direct him to the store and now it says Not Secure. That did more to explain the situation than my attempt at TLS and HTTPS and Certs. He was able to cal…
If that doesn't work, there's also the argument that "credit card providers require it, and could stop you from taking credit cards until you fix it".