4 ms·
Considering that latey there's been a pretty strong shift to using HTTPs everywhere, I don't see how using it on .gov site needs an explanation :)
by gear54rus 12y ago
Considering that latey there's been a pretty strong shift to using HTTPs everywhere, I don't see how using it on .gov site needs an explanation :)
- konklone 12y ago> Considering that latey there's been a pretty strong shift to using HTTPs everywhere, I don't see how using it on .gov site needs an explanation :) If only the .gov space were shifting at the same rate! That sense of inevitability and momentum you sense in the private sector is not so widely present inside the US government. Posts like this have two audiences: outside folks like you, and my colleagues around the rest of the .gov world. For reference, 18F got the first .gov domains added to the Chrome HSTS preload list less than 2 weeks ago: https://chromium.googlesource.com/chromium/src/+/af1870543d1be92e4fb1560f7c8ed2412c24ff5f%5E%21/#F1 https://chromium.googlesource.com/chromium/src/+/af1870543d1...
- MertsA 12y agoWell you're moving faster than all of the major banks in America. All of the top 5 or so banks that I checked don't bother with HSTS.
- higherpurpose 12y agoYou'd think that would've happened years ago, after all the "protecting our infrastructure" and "cyberthreats" rhetoric from certain parts of the government.
- mpyne 12y agoSadly, it's not rhetoric. Also sadly, yes you would think some progress would have started years ago.