It seems there is no standard proper way to store private keys.<p>I have been using AGE [0]<p>And I really don't like the idea of having the keys stored in the home directory in plain text.<p>There is also a risk of losing the keys if my laptop is damaged or gets stolen.<p>Is there a proper tool for storing encryption keys?
> It seems there is no standard proper way to store private keys.<p>The gold standard for this would be a Hardware Security Module (HSM), which is essentially a device that stores private keys with certain guarantees of physical security (e.g, that private key material cannot be extracted from the device once it has been generated or placed there, and the device performs operations using the key material on behalf of some client).<p>HSMs in various forms underpin all sorts of cryptosystems that society depends on, because securing private key material at rest is essential. You'll find them everywhere from your debit/credit card, to certificate authorities, financial institutions, defense, and your smartphone.<p>For your use case, I'd recommend taking a look at Yubikeys. I did a writeup a while back on how to use them to store different types of private keys for various purposes:<p><a href="https://blog.ctis.me/2022/12/yubikey-piv-gpg/" rel="nofollow">https://blog.ctis.me/2022/12/yubikey-piv-gpg/</a>
1Password with their SSH agent [1] for SSH keys, their CLI [2] for local secrets, and their terraform provider with service tokens for infrastructure keys/secrets. Yubikey for the secrets I’m most paranoid about.<p>You can essentially encrypt all environment variables, not just SSH keys, by aliasing your terminal commands to the 1password CLI. I have a “secrets” repo where all dotenv files are checked in with values like “op://vault-name/secret-name/key-name” that get injected by the op cli.<p>[1] <a href="https://developer.1password.com/docs/ssh/agent/" rel="nofollow">https://developer.1password.com/docs/ssh/agent/</a><p>[2] <a href="https://developer.1password.com/docs/cli/get-started/" rel="nofollow">https://developer.1password.com/docs/cli/get-started/</a>
Paper. There’s a project called paperkey that allows you to store GPG keys on A4 paper. You could apply a similar approach to your age encrypted private keys or store them in plain text.<p>Modern smartphones have excellent OCR (optical character recognition) capabilities, so converting images of printed text back into digital form is now quite easy and reliable.<p>Personally, I use 1Password, and even they recommend printing out a PDF copy of your passwords and storing it in a secure location - like a physical vault. It’s a practical backup in case something happens and someone needs access to your credentials.
> And I really don't liek the idea of having the keys stored in the home directory in plain text.<p>so encrypt them.<p>or store them in a hardware token.<p>or on a USB stick (poor man's hardware token).<p>> There is also a risk of losing the keys if my laptop is damaged or gets stolen.<p>backups, full disk encryption.
I have previously written a blog post on this very topic, tl;dr: deleting your keys.<p><a href="https://blog.imcotton.xyz/my-ssh-folder-has-no-private-keys" rel="nofollow">https://blog.imcotton.xyz/my-ssh-folder-has-no-private-keys</a>
if you're referring to SSH keys, you can use something like 1Password which stores them encrypted and syncs them in the cloud, so you keep them even if you lose your laptop