ui_puttygen » Revisions »
Differences
This shows you the differences between the selected revisions of the page.
| 2021-12-06 | 2021-12-06 | ||
| 5.20 Removed support for SSH-1 (martin) | no need to refer to ssh versions (martin) | ||
| Line 31: | Line 31: | ||
| Before generating a key pair using PuTTYgen, you need to select which type of key you need. | Before generating a key pair using PuTTYgen, you need to select which type of key you need. | ||
| - | The current version of the SSH protocol, SSH-2, supports several different key types, although specific servers may not support all of them. PuTTYgen can generate: | + | The SSH protocol supports several different key types, although specific servers may not support all of them. PuTTYgen can generate: |
| - | * An RSA key for use with the %%SSH-2%% protocol. | + | * An RSA key. |
| - | * A DSA key for use with the %%SSH-2%% protocol. | + | * A DSA key. |
| - | * An ECDSA (elliptic curve %%DSA%%) key for use with the %%SSH-2%% protocol. | + | * An ECDSA (elliptic curve %%DSA%%) key. |
| - | * An EdDSA key (Edwards-curve DSA, another elliptic curve algorithm) for use with the %%SSH-%%2 protocol. | + | * An EdDSA key (Edwards-curve DSA, another elliptic curve algorithm). |
| - | PuTTYgen can also generate an %%RSA%% key suitable for use with the old %%SSH-1%% protocol (which only supports %%RSA%%). But SSH-1 is no longer supported by WinSCP. | + | PuTTYgen can also generate an %%RSA%% key suitable for use with the deprecated %%SSH-1%% protocol (which only supports %%RSA%%). But SSH-1 is no longer supported by WinSCP. |
| ===== [[size]] Selecting the Size (Strength) of the Key ===== | ===== [[size]] Selecting the Size (Strength) of the Key ===== | ||
| Line 128: | Line 128: | ||
| ===== [[saving_public]] Saving Your Public Key to a Disk File ===== | ===== [[saving_public]] Saving Your Public Key to a Disk File ===== | ||
| - | RFC 4716 specifies a standard format for storing SSH-2 public keys on disk. Some SSH servers (such as ssh.com's) require a public key in this format in order to accept authentication with the corresponding private key. (Others, such as OpenSSH, use a different format) | + | RFC 4716 specifies a standard format for storing SSH public keys on disk. Some SSH servers (such as ssh.com's) require a public key in this format in order to accept authentication with the corresponding private key. (Others, such as OpenSSH, use a different format) |
| - | To save your public key in the SSH-2 standard format, press the //Save public key// button in PuTTYgen. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press //Save//. | + | To save your public key in the SSH standard format, press the //Save public key// button in PuTTYgen. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press //Save//. |
| You will then probably want to copy the public key file to your SSH server machine. | You will then probably want to copy the public key file to your SSH server machine. | ||
| Line 182: | Line 182: | ||
| ===== [[other_formats]] Dealing with Private Keys in Other Formats ===== | ===== [[other_formats]] Dealing with Private Keys in Other Formats ===== | ||
| - | SSH-2 private keys have no standard format. OpenSSH and ssh.com have different formats, and WinSCP's is different again. So a key generated with one client cannot immediately be used with another. | + | SSH private keys have no standard format. OpenSSH and ssh.com have different formats, and WinSCP's is different again. So a key generated with one client cannot immediately be used with another. |
| - | Using the //Import// command from the //Conversions// menu, PuTTYgen can load SSH-2 private keys in OpenSSH's format and ssh.com's format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key (''*.PPK'') so that you can use it with the WinSCP. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since some OpenSSH key formats contained no space for a comment, and ssh.com's default comment format is long and verbose. | + | Using the //Import// command from the //Conversions// menu, PuTTYgen can load SSH private keys in OpenSSH's format and ssh.com's format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key (''*.PPK'') so that you can use it with the WinSCP. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since some OpenSSH key formats contained no space for a comment, and ssh.com's default comment format is long and verbose. |
| PuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the //Export// options from the //Conversions// menu. Exporting a key works exactly like [[#saving_private|saving it]] -- you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase. | PuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the //Export// options from the //Conversions// menu. Exporting a key works exactly like [[#saving_private|saving it]] -- you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase. | ||