X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fpubkey.but;h=137dba233a5b1c1c01367968d4d9f697b34ca19d;hb=f004bcca17a789356c32527a396b68b71a773db2;hp=db4431c50b51760784615b0629fb7851f3ca7e2d;hpb=908acc3adbeecc664a59c5d211012aa942221ba5;p=PuTTY.git diff --git a/doc/pubkey.but b/doc/pubkey.but index db4431c5..137dba23 100644 --- a/doc/pubkey.but +++ b/doc/pubkey.but @@ -1,5 +1,3 @@ -\define{versionidpubkey} \versionid $Id$ - \C{pubkey} Using public keys for SSH authentication \H{pubkey-intro} \ii{Public key authentication} - an introduction @@ -151,18 +149,6 @@ of the key PuTTYgen will generate. Currently 1024 bits should be sufficient for most purposes. -Note that an RSA key is generated by finding two primes of half the -length requested, and then multiplying them together. For example, -if you ask PuTTYgen for a 1024-bit RSA key, it will create two -512-bit primes and multiply them. The result of this multiplication -might be 1024 bits long, or it might be only 1023; so you may not -get the exact length of key you asked for. This is perfectly normal, -and you do not need to worry. The lengths should only ever differ by -one, and there is no perceptible drop in security as a result. - -DSA keys are not created by multiplying primes together, so they -should always be exactly the length you asked for. - \S{puttygen-generate} The \q{Generate} button \cfg{winhelp-topic}{puttygen.generate} @@ -243,7 +229,7 @@ If you leave the passphrase fields blank, the key will be saved unencrypted. You should \e{not} do this without good reason; if you do, your private key file on disk will be all an attacker needs to gain access to any machine configured to accept that key. If you -want to be able to \i{passwordless login}log in without having to +want to be able to \I{passwordless login}log in without having to type a passphrase every time, you should consider using Pageant (\k{pageant}) so that your decrypted key is only held in memory rather than on disk.