News for hackers. Stuff that matters.
Re:Chrome to force .dev domains to HTTPS via preloaded HSTS by xg15 on Sunday September 17, 2017 @12:00PM (#15270213)
> And for the last question: Again, there are no .dev domain names. There never have been. It's never been available for registration.

It is, however, in widespread practical use.

> The recommendation for a long time has been to only use either (a) domain names that you actually own, or (b) domain names that are reserved for testing and are guaranteed never to exist a la RFC 2606

If taken to its extreme, that recommendation would mean that any kind of internal hostnames - even dotless ones - are subject to potential override unless they are tied to a public DNS entry.

Re:Chrome to force .dev domains to HTTPS via preloaded HSTS by JdeBP on Sunday September 17, 2017 @02:18PM (#15270910)
As indeed they actually are. WWW browsers have a search path, that is added on to a second search path mechanism that DNS client libraries have. Domain names with dots in, but that are not fully qualified, suffer from this. Yes, this means that what http://wibble/ is right now is subject to change; and even http://wibble.wobble/ could be, depending from various factors.

* http://jdebp.eu./FGA/web-fully-qualified-domain-name.html

Would that I had recorded the case some while back where, when I pointed this out, someone chimed in to note that xe had worked for a company that had actually taken advantage of this in order to usurp external WWW sites.

And then there was WPAD.

* http://jdebp.eu./FGA/web-browser-auto-proxy-configuration.ht...

This is not taking things to an extreme. This is reality right now and has been for many years.

Re:Chrome to force .dev domains to HTTPS via preloaded HSTS by xg15 on Monday September 18, 2017 @05:07AM (#15274371)
I wasn't aware of that. Thanks for the info!
Re:Chrome to force .dev domains to HTTPS via preloaded HSTS by detaro on Sunday September 17, 2017 @01:04PM (#15270549)
Yes. That's why it's recommended to have a subdomain of a domain you own under which all internal names live. (no need for it/them being in public DNS though)