
Requests changing the comment in the private and public key files. Key sizes above that no longer improve security but make things slower. Generally, 1024 bits is considered sufficient. Specifies the number of bits in the key to create. The following options are supported: -b bits The comment is initialized to `` the key is created, but can be changed using the -c option.Īfter a key is generated, instructions below detail where to place the keys to activate them. The comment can tell what the key is for, or whatever is useful. If the passphrase is lost or forgotten, you will have to generate a new key and copy the corresponding public key to other machines.įor RSA, there is also a comment field in the key file that is only for convenience to the user to help identify the key. There is no way to recover a lost passphrase. (English prose has only 1-2 bits of entropy per word, and provides very poor passphrases.) The passphrase can Good passphrases are 10-30 characters long and are not simple sentences or otherwise easy to guess. Passphrase (host keys must have empty passphrases), or it may be a string of arbitrary length. The passphrase may be empty to indicate no The public key is stored in a file with the same name but with the ``. Ordinarily, this program generates the key and asks for a file in which to store the private key. ssh-keygen defaults to generating an RSA key for useĮach user wishing to use SSH with RSA or DSA authentication normally runs this once to create the authentication key in $HOME/.ssh/identity or $HOME/.ssh/id_dsa. The ssh-keygen utility generates and manages authentication keys for ssh(1).
