5 ms·
Hey everyone. I'm the Tech Lead of Google Registry and I'm the one behind this (and likely future) additions to the HSTS preload list. I might be able to answ
by CydeWeys 9y ago
Hey everyone. I'm the Tech Lead of Google Registry and I'm the one behind this (and likely future) additions to the HSTS preload list. I might be able to answer some questions people have.
But to pre-emptively answer the most likely question: We see HTTPS everywhere as being fundamental to improving security of the Web. Ideally all websites everywhere would use HTTPS, but there's decades of inertia of that not being the case. HSTS is one tool to help nudge things towards an HTTPS everywhere future, which has really only become possible in the last few years thanks to the likes of Let's Encrypt.
- drivingmenuts 9y agoYeah, that's awesome, but many of us do test on our local machines where https would just be an extra layer of annoyance and having to use .localhost TLD would be icing on that annoying cake. Since it appears that .dev is a Google internal TLD, would you consider not forcing that rule outside of Google? Effectively, we're getting all the stick and none of the carrot. Alternately, announce your plans for .dev so as to bring some transparency to the process OR purchase maybe the .vm TLD and mark it for developer local testing in place of/addition to .localhost.
- CydeWeys 9y ago.dev is not an internal Google TLD. It is delegated but not yet launched (i.e. made available for registration). We don't use it for anything internally. You should not be using globally delegated TLDs for local testing. See RFC 2606. I don't see how using .localhost or .test is any more of an inconvenience than using .dev. Indeed it is less of an inconvenience because it will work without DNS shenanigans. The last round of gTLD expansion occurred in 2012 and there's still many years left until a potential future round. Additionally, .vm is not a valid gTLD because all two letter combinations are reserved for ccTLDs (countries). And I would love to have some plans to announce. Maybe soon.
- thawkins 9y agoWhat about providing a config switch in chrome etc to disable the new behaviour, so those of us that use .dev in our workflow can turn off the redirection.
- CydeWeys 9y agoYou should not be using domain names on .dev unless you own them (which no one does .. yet). If you choose to do so it's at your own risk.
- dylz 9y agoYou never should have been using it, though? It wasn't your domain to begin with or your TLD. It's like complaining that you're using appname.ycombinatordev.com as a development suffix, then someone registers it and all your stuff breaks, and you want them to fix your problem. It isn't good practice to use random domains or TLDs that you don't own for testing. At work we have a separate publicly-registered domain, and an internal subdomain with NS records on the primary publicly-registered domain that resolves separately. It's never been a problem..
- wolco 9y agoDo you think this plan might encourage developers to develop using another browser?
- panic 9y agoOne of greatest things about the Web is how easy it is to write HTTP clients and servers. I see why HTTPS everywhere would be helpful, but I also think it would be a shame to lose this simplicity. Has there been any thought put toward simpler alternatives to HTTP+TLS?
- CydeWeys 9y agoThat's way outside my area of expertise. I don't think HTTPS is that bad anymore, not now that certificates are easy to obtain. What are your biggest pain points? More broadly, I think it's worth incurring some inconvenience for the sake of security. Go too far in the other direction and you end up like Equifax.
- AndyMcConachie 9y agoYou may want to read up on DANE. https://tools.ietf.org/html/rfc6698 https://tools.ietf.org/html/rfc6698 Not really an alternative to HTTP+TLS, but possibly another way of doing it depending on how it's implemented.
- jopsen 9y agoThink of all the time we heard about people stealing passwords from HTTP over wifi networks.. Forcing security at multiple levels and making HTTPS easier is the way forward.
- hungerstrike 9y agoI bet you can't answer the actual most likely question: What are you (Google) planning on doing with .dev domains anyway? However besides that...just curious: Will Chrome honor a header to disable HSTS for preloaded domains? (e.g. Strict-Transport-Security: max-age=0)? And what is going to happen if I submit my .dev site for removal from https://hstspreload.org/ https://hstspreload.org/ ? Also, reading the rules on hstspreload.org, I see the following statement: "Don't request inclusion unless you're sure that you can support HTTPS for your entire site and all its subdomains the long term" Since you cannot actually guarantee that every .dev site will support HTTPS considering the fact that many developers use it on their LAN...don't you think you're breaking the rules here and possibly causing more problems than solutions?
- CydeWeys 9y agoI would love to be able to answer that first question for you. Unfortunately I have nothing to share yet. My understanding is that HSTS carveouts are supported by Chrome but not yet other browsers. There's more standardization work to be done there. That said, you can only request entries on the HSTS list for domains that you own, and since no one (yet?) owns any .dev domain names, no one could request such changes. It goes without saying why you can only change security settings for domain names that you own. And for the last question: Again, there are no .dev domain names. There never have been. It's never been available for registration. 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. Using domain names for testing that don't yet exist but could in the future is a huge security hole that you must fix now. Do it now while the domain names still fail to resolve. Once they resolve, and you don't own them, then your security situation gets a lot worse.
- xg15 9y ago> 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.
- AndyMcConachie 9y agoDo you plan on DNSSEC signing subdomains of Google's TLDs? For example, I see that .dev has a DS record in the root. But nic.dev is not signed.
- greggman 9y agoDo you have a solution for IoT devices that want to serve a webpage with HTTPS? For example my router or an IP camera?
- e12e 9y agoSo, kill off lan-level caching http proxy servers? (Or force a choice between trust the cache with everything; including email etc - or - no caching of signed software updates and common media resources?) I'd be less unhappy about this if web browsers (and application updaters) understood x509 ca cert limits, so you could tell a device to trust the lan cache to impersonate Debian.org, windowsupdate.com and BBC.com - but not Gmail.com...