News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ocdtrekkie on Thursday February 08, 2018 @07:53PM (#16336996)
The problem is when Google goes and throws a commonly used internal-only TLD like .dev in their HSTS list. And of course, the whole problem that HSTS is the hosts file all over again.

That being said, the real fault in that incident is ICANN selling .dev in the first place. They should've been well aware of it's common use, and opted not to sell it.

Re:Chrome 68 will mark all HTTP sites as “not secure” by sattoshi on Thursday February 08, 2018 @09:50PM (#16337542)
I have a theory that ICANN did this too tell developers to use designated domains for internal uses.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ocdtrekkie on Thursday February 08, 2018 @10:06PM (#16337604)
I think you're putting too much thought into it. It's very simple: .dev is a massively easy to monetize TLD, it was guaranteed to get multiple companies trying to buy it, and when they had multiple offers, they got auctioned.

I think .dev was just too much money for ICANN to say no.

Of course, it looks like ICANN may have gotten screwed, because Amazon and Google appear to have privately arranged to figure out who was going for which TLDs: https://icannwiki.org/.dev