3 ms·
So did they conclude it wasn’t a security concern or did they conclude the security risk was worth the uptime?
by mc32 8y ago
So did they conclude it wasn’t a security concern or did they conclude the security risk was worth the uptime?
- mehrdadn 8y agoI'm curious as well. My intuition would be that it's not a concern, since servers already keep their private keys stored locally in order to be able to communicate with clients anyway? Being able to update them doesn't really seem to make things any different. But I feel like I could be missing something/not have thought through it properly. (I imagine security implications can get more complicated if a different server decrypts traffic vs. processes it, etc.)
- revvx 8y agoThe "manual" process used previously by the company already involved some form of automation, so it was more about trusting CertBot not to do anything horrendous. But now that you mention it, I wonder what's the opinion of security experts like tptacek on cert renewal automation.
- inflatableDodo 8y agoWe could attempt a summoning. Quick, make a wildly inaccurate claim about the correct way to implement an encryption library.
- revvx 8y agoWhen pressed, they admitted it was just "gut feeling". The team audited a couple ACME clients and couldn't find anything to justify not automating.
- dingaling 8y agoHaving a root process with write-privileges to /etc on production machines and also able to communicate over the Internet definitely is a security risk. To mitigate that you end-up building a series of privilege-restricted jobs flowing from the DMZ back into the internal network. And maintaining that might be more complicated than just manually renewing, depending upon the processes and architecture of the company.
- Whitestrake 8y agoWhy would a process need to run as root or have write privileges to /etc in order to automate LetsEncrypt renewals? I run Caddy (which uses acme-go/lego as its ACME provider) as a non-root user with no access to /etc at all. It seems to be running fine.
- tedunangst 8y agoDepends on setup, but frequently private keys are inaccessible to the web server worker process. (Which starts as root, loads keys, drops privs, etc.)
- tialaramex 8y agoMost popular ACME (Let's Encrypt) clients allow you to provide a CSR instead of generating the keys themselves. That means a bunch more work for you, but if you're worried about this, that's what you should do. Have your safe (even manual if you insist) process make keys, make CSRs for the keys, and put those somewhere readable. The ACME client will hand them over to the CA saying "I want certs corresponding to these CSRs" without needing access to your TLS private keys at all.
- rocqua 8y agoThat does mean you aren't automatically rotating keys anymore.
- revvx 8y agoIf you trust your automation, you put private key rotation into it. If you don't trust it your automation, you rotate the keys manually, as you would normally. There are no valid reasons to throw the baby away with the bathwater.
- rocqua 8y agoUsing http renewal requires listening on port 80 which, by default, requires root.