4 ms·
The employees tasked with clicking the "Renew Certificate" button every X months probably have no idea how they'd go about that. As a contracting project, I im
by pavlov 8y ago
The employees tasked with clicking the "Renew Certificate" button every X months probably have no idea how they'd go about that.
As a contracting project, I imagine it would be pretty expensive to upgrade every single website of the US federal government to use Let's Encrypt. How many different operating systems and web server setups there must be?
- tomohawk 8y agoMy point is that said employees / contractors should have a better plan than having to be there at a certain time to push a button. That's planning for failure. What if the contract has a problem? It happens. What if the approving official is out sick for a month? It happens. Not knowing how to set these things up? I don't really think that's an excuse. This should be addressed in the requirements.
- pavlov 8y agoFederal agencies have made websites for the past 25 years. Let's Encrypt launched in 2016. It's bleeding-edge technology as far as public sector requirements go.
- deleted 8y ago[deleted]
- beat 8y agoMethinks a lot of the eyerolling about not using Let's Encrypt is coming from people who have never touched a real legacy system in their lives.
- tomohawk 8y agoSpecifying requirements for uptime is not new. Federal agencies have many failure modes that are different than private sector, but those who work there know about them. Purchasing a 1 year cert can be extremely challenging, depending on the agency, due to procurement rules, etc. For such an important part of a site to be neglected when the above is known - an eye roll is about all the respect that can be afforded to it. Source: I've worked in and with the federal government for more than 25 years.
- beat 8y agoDone fed-wide, it would make more sense to set up the federal government as a top-level certificate authority, and build a LetsEncryptAlike that does the same thing.
- colek42 8y agoThis would be amazing. Certificates are always a pain when I work with the federal government. Many times they just self-sign which causes a ton of extra work to do something simple, such as pulling from a private registry.
- beat 8y agoIt's not just government... a lot of big enterprise corporations have the same problem. Even internally.