![]() ![]() No matter which command you chose, you should see something like: The authenticity of host '12.34.56.78 (12.34.56.78)' can't be established. ssh-copy-id you can paste in the keys using SSH: cat ~/.ssh/id_rsa.pub | ssh "mkdir -p ~/.ssh & cat > ~/.ssh/authorized_keys" Make sure to replace the example username and IP address below. You can copy the public key into the new machine’s authorized_keys file with the ssh-copy-id command. Once the key pair is generated, it’s time to place the public key on the virtual server that we want to use. The public key is now located in /home/demo/.ssh/id_rsa.pub The private key (identification) is now located in /home/demo/.ssh/id_rsa ![]() Your identification has been saved in /home/demo/.ssh/id_rsa. The entire key generation process looks like this: ssh-keygen -t rsaĮnter file in which to save the key (/home/demo/.ssh/id_rsa):Įnter passphrase (empty for no passphrase): The only downside, of course, to having a passphrase, is then having to type it in each time you use the Key Pair. Should a passphrase-protected private key fall into an unauthorized users possession, they will be unable to log in to its associated accounts until they figure out the passphrase, buying the hacked user some extra time. Entering a passphrase does have its benefits: the security of a key, no matter how encrypted, still depends on the fact that it is not visible to anyone else. It’s up to you whether you want to use a passphrase. Enter passphrase (empty for no passphrase): You can press enter here, saving the file to the user home (in this case, my example user is called demo). Once you have entered the Gen Key command, you will get a few more questions: Enter file in which to save the key (/home/demo/.ssh/id_rsa): ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |