News for hackers. Stuff that matters.

A comment on Chrome 68 Released: HTTP Sites Marked as “Not Secure”. Parent comment

Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by matthewmacleod on Wednesday July 25, 2018 @04:53AM (#17607822)
Yes, that's right – because it _is_ insecure, fundamentally.

These sites will continue to be entirely accessible, so I have no idea what solution you think is required. If a provider wants to upgrade such that their site is no longer insecure, then they can pay to upgrade it themselves.

[ Parent | on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by mynewaccount0 on Wednesday July 25, 2018 @06:32AM (#17608209)
This is absolutely, entirely wrong. It's so wrong that I need to wonder why you don't even realize you're wrong. A HTTP website with my GPG-signed data is _more_ secure than an HTTPS website. Relying on a CA is not the only way to secure a website. But this isn't about securing websites, this is about forcing us to rely on CAs.
[ Parent | on HN ]