nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 11:32:48 -05:00
Code Issues Projects Releases Wiki Activity

UI changes for key imports. We now have a separate Load command and

Browse Source 
Import command; the former warns you if you load a foreign key,
whereas the latter doesn't. So the user should always be aware, one
way or the other, that a format conversion is taking place.

[originally from svn r1687]
This commit is contained in:
Simon Tatham
2002-05-18 09:20:41 +00:00
parent 8cdae4f73b
commit c92ea6c8ed
2 changed files with 59 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
doc/pubkey.but
View File

@ -1,4 +1,4 @@
\versionid $Id: pubkey.but,v 1.16 2002/05/16 22:36:36 jacob Exp $
\versionid $Id: pubkey.but,v 1.17 2002/05/18 09:20:41 simon Exp $
\C{pubkey} Using public keys for SSH authentication
@ -330,17 +330,14 @@ find your key file. Once you select the file, PuTTYgen will ask you
for a passphrase (if necessary) and will then display the key
details in the same way as if it had just generated the key.
PuTTYgen can also load SSH2 private keys in OpenSSH's format and
\cw{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 so that you can
use it with PuTTY. The passphrase will be unchanged by this process.
You may want to change the key comment before you save the key,
since OpenSSH's SSH2 key format contains no space for a comment and
\cw{ssh.com}'s default comment format is long and verbose.
If you use the Load command to load a foreign key format, it will
work, but you will see a message box warning you that the key you
have loaded is not a PuTTY native key. See \k{puttygen-conversions}
for information about importing foreign key formats.
\S{puttygen-export} Exporting your private key in an alternative format
\S{puttygen-conversions} Dealing with private keys in other formats
\cfg{winhelp-topic}{puttygen.export}
\cfg{winhelp-topic}{puttygen.conversions}
Most SSH1 clients use a standard format for storing private keys on
disk. PuTTY uses this format as well; so if you have generated an
@ -352,15 +349,25 @@ However, SSH2 private keys have no standard format. OpenSSH and
So a key generated with one client cannot immediately be used with
another.
PuTTYgen has the ability to export private keys in OpenSSH format,
or in \cw{ssh.com} format. To do so, select an option from the
\q{Export} menu at the top of the PuTTYgen window. Exporting a key
works exactly like saving it (see \k{puttygen-savepriv}) - 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.
Using the \q{Import} command from the \q{Conversions} menu, PuTTYgen
can load SSH2 private keys in OpenSSH's format and \cw{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 so that you can use it with
PuTTY. 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 OpenSSH's SSH2 key format contains no
space for a comment and \cw{ssh.com}'s default comment format is
long and verbose.
Note that the export options are only available if you have
generated an SSH2 key.
PuTTYgen can also export private keys in OpenSSH format and in
\cw{ssh.com} format. To do so, select one of the \q{Export} options
from the \q{Conversions} menu. Exporting a key works exactly like
saving it (see \k{puttygen-savepriv}) - 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.
Note that since only SSH2 keys come in different formats, the export
options are not available if you have generated an SSH1 key.
\H{pubkey-gettingready} Getting ready for public key authentication