4 ms·
You must be kidding. This is encryption 101. The private key is supposed to be moved to a secure location after key generation.
by aioprisan 13y ago
You must be kidding. This is encryption 101. The private key is supposed to be moved to a secure location after key generation.
- tbrownaw 13y agoEr, what? I thought the keypair was supposed to be generated in a secure location (such as your 0700 mode ~/.ssh directory), and then only the public half ever leaves.
- tailrecursion 13y agotwbrownaw is exactly right. If the private key is already in a secure location then there is no need to move it to a secure location. So, any report that the public keys were stored with the private keys means nothing by itself.
- jmillikin 13y agoYou are arguing that storing the public and private key in a vault under the ocean is not less secure than just storing the private key there. While that is technically true, it's also missing the point.
- icebraining 13y agoHow is it missing the point? It tells us that having "both keys in one directory" is, by itself, no evidence of insecurity by Linode.
- deleted 13y ago[deleted]
- dllthomas 13y agoAs others have said: a private key should never be in an insecure location, or it's no longer secure. You have to generate it in a secure location, and since you're generating the key-pair, you'll have both your public and private keys in the same (secure) location until you remove the public key, which I don't see any strong reason to do.
- marshray 13y agoEncryption 101.1: move signatures and ciphertext, don't move (non-public) keys.