News for hackers. Stuff that matters.
Re:Ask HN: How does your company manage its encryption keys? by dijit on Tuesday June 02, 2020 @10:16AM (#23391233)
Not sure the "right" way to do it. But this is what we did:

For context: We run a centralised salt-master, salt master unencrypts content using gpg filters as part of variable generation (salt "pillars"). So it's encrypted at rest and encrypted in our git repositories.

What we do/did, is:

* grab a pair of differently branded USB sticks.

* LUKS encrypt the USB sticks; we used a keyfile which is encrypted on our machines with our GPG key.

* encrypt salt's GPG private key with all of our keys.

* encrypt some of the "irreplacable" private keys (IE: CA roots) with all of our GPG keys.

* store it all on the pair of USB drives

* put the USB drives in a real-life vault, give the keys to the office team.

We haven't needed to recover, but it's clearly documented how to recover if anything went wrong.

Re:Ask HN: How does your company manage its encryption keys? by openfuture on Tuesday June 02, 2020 @10:58AM (#23391701)
Bit rot is a thing.

It'd be better to take a page out of the cryptocurrency handbook and print the keys out as QR codes (maybe with a simple password so it can only be restored if you know the pw).

Re:Ask HN: How does your company manage its encryption keys? by jeremygaither on Thursday June 04, 2020 @12:31PM (#23418710)
How do you handle the LUKS key file? Do you encrypt it to the whole team? Just yourself? How do you circulate that LUKS key file?
Re:Ask HN: How does your company manage its encryption keys? by frabbit on Thursday June 04, 2020 @12:44PM (#23418847)
Why differently branded?