Skip to content

Comment on Chrome and misleading security informationparent

Comments

yes, I picked on Chrome just because that's what I was using at the time, I am aware the problem probably exists on most browsers.

As I stated in my reply, that's not a bug, that's a feature; sorry to hear it's inconveniencing you, but there is currently no other way to distinguish between https://yourbank.example.com/ and a MITM by https://phishingsite.evil/

Replacing a CA-based chain of trust with a Google-based chain of trust makes no difference IMNSHO (except that Google would essentially own and 0wn the Internet; not a pleasant side-effect).

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.