3 ms·
"After some research, we found this blog post by Mattias Geniar, which explained how Google was forcing .dev domains to be served via HTTPS through a preloaded
by 1vuio0pswjnm7 4y ago
"After some research, we found this blog post by Mattias Geniar, which explained how Google was forcing .dev domains to be served via HTTPS through a preloaded HSTS setting in their Chrome browsers - which Firefox later adopted too."
Imagine if Google did not have and control its own browser, Chrome. In theory then Google could not force the author to purchase a .dev.domain. What's sad here is that according to the author Mozilla has followed Google's lead. Note this has nothing to do with fact that Mozilla's main source of income is Google, and Chrome was developed by former Mozilla employees who went to work for Google.
It is possible to use a browser other than Chrome or Firefox (or Safari, Edge, Brave, etc.) that has no XSS risk because the browser does not auto-load resources. This alleviates need for HSTS as a means to prevent XSS (NB. there are other purported justifications for using HSTS besides preventing XSS). How do I know it is possible. Because I use one. For recreational web use, like reading sites submitted to HN. Freedom of choice.
It's also possible to run a localhost-bound forward proxy where one can set HSTS to whatever value one desires, or remove the header entirely. Instead of relying on an advertising company, one can use the proxy to "upgrade" http:// http:// to https:// https://. All outgoing HTTP requests can be encrypted and connections to local port 80 can be forwarded to remote 443. I know it's possible because this is what I do. Unlike HSTS, the proxy "fixes" any application sending HTTP requests, not only a browser that supports HSTS. The proxy can also limit the sites the user wishes to trust.^1
That is the real issue I have with HSTS. It further removes (i.e., makes more difficult) the ability of the user to determine what sites she will trust, placing that decision in the hands of third parties, namely those that control the "CA system". It's already annoying enough that Chrome forces users to type a shibboleth into a keylogger to get past certificate warnings. HSTS makes it even more annoying. It is unfriendly for users who in some situations trust their own decision-making more than they trust Google and CAs.
"At first, we thought we could opt out of HSTS preload, but it doesn't seem like that'd be possible. Even if you access your Chrome's HSTS settings via chrome://net-internals/#hsts, you'll see Google doesn't allow you to remove preloaded HSTS entries."
This is telling. The risk of a user inadvertently disabling HSTS is close to zero. This is plain and simple removal of the ability of the user to control the program.
One option for users is to remove the entries in the Chromium source then re-compile.