X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fpubkey.but;h=137dba233a5b1c1c01367968d4d9f697b34ca19d;hb=a063e522970946bf7d5dc052079d7773c0dee76d;hp=ee4b600b3698d0327d57fdd6932691632e14571d;hpb=fece1b69f56d9f1252b54a431030d4bb3ae4dbbe;p=PuTTY.git

diff --git a/doc/pubkey.but b/doc/pubkey.but
index ee4b600b..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}