1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00

Tweaks to OpenSSH key format docs.

Index the older format as 'PEM-style', since PEM is how it's referred to
in OpenSSH's own docs; and justify why you might want to use the newer
format.
This commit is contained in:
Jacob Nevins 2023-07-12 17:55:58 +01:00
parent 05a6699939
commit 9ce5bc401c
2 changed files with 9 additions and 2 deletions

View File

@ -869,6 +869,9 @@ saved sessions from
\IM{ssh.com private key format} \cw{ssh.com} private key file format
\IM{ssh.com private key format} private key file, \cw{ssh.com}
\IM{PEM-style} PEM-style OpenSSH private key format
\IM{PEM-style} OpenSSH private key format, PEM-style
\IM{importing keys} importing private keys
\IM{importing keys} loading private keys

View File

@ -507,13 +507,17 @@ passphrase in beforehand, and you will be warned if you are about to
save a key without a passphrase.
For OpenSSH there are two options. Modern OpenSSH actually has two
formats it uses for storing private keys. \q{Export OpenSSH key}
formats it uses for storing private keys: an older (\q{\i{PEM-style}})
format, and a newer \q{native} format with better resistance to
passphrase guessing and support for comments. \q{Export OpenSSH key}
will automatically choose the oldest format supported for the key
type, for maximum backward compatibility with older versions of
OpenSSH; for newer key types like Ed25519, it will use the newer
format as that is the only legal option. If you have some specific
reason for wanting to use OpenSSH's newer format even for RSA, DSA,
or ECDSA keys, you can choose \q{Export OpenSSH key (force new file
or ECDSA keys \dash for instance, you know your file will only be
used by OpenSSH 6.5 or newer (released in 2014), and want the extra
security \dash you can choose \q{Export OpenSSH key (force new file
format)}.
Most clients for the older SSH-1 protocol use a standard format for