prepare for upload, add Franck as uploader

[pgp-tools.git] / caff / README.many-keys

diff --git a/caff/README.many-keys b/caff/README.many-keys
index ce57d5ece656360aa8339204da3897e95436959e..6e46bc444415fc40047e7a12944e8269eacd8e4e 100644 (file)
--- a/caff/README.many-keys
+++ b/caff/README.many-keys
@@ -2,7 +2,7 @@ Using caff to sign lots of keys
 -------------------------------
 
 If you have loads of keys to sign (sometimes, there are keysigning parties with
-more than 100 participants), keysigning can be arkward, even with caff. It gets
+more than 100 participants), keysigning can be awkward, even with caff. It gets
 worse if you have multiple local keys and want to sign with all.
 
 Some hints to get the signing done faster:
@@ -13,31 +13,50 @@ Some hints to get the signing done faster:
   from having to check the fingerprint yourself. If you have a text file with
   all fingerprints, use that and then run
 
-  $ caff <options> `cat ksp-fingerprints.txt`
+  $ caff <options> "`cat ksp-fingerprints.txt`"
+
+  For convenience, caff also allows spaces in fingerprints/keyids as output by
+  gpg --fingerprint. (Remember to properly quote arguments as shown above.)
 
 * v3 keys are evil.
 
-  Sign v3 separately. Batch processing does not work. See README.v3-keys.
+  V3 keys (pgp 2.6x keys) are deprecated.  Not only do they rely on md5 for
+  their fingerprint and signatures, they also use the patented IDEA algorithm
+  for encryption.  Also, there are several attacks that make creating new keys
+  with the same keyid trivial.  Others make it possible to create different
+  keys with the same fingerprint (tho the key will not actually contain valid
+  RSA parameters).
+
+  Because of these problems a lot of people (like caff's author) refuse to sign
+  v3 keys these days.
+
+  If you still want to sign v3 keys, sign v3 separately. Batch processing does
+  not work. See README.v3-keys.
 
 * Use multiple passes.
 
   Going through retrieving, signing, and mailing keys can help, e.g.:
 
-  $ caff -SEM `cat ksp-fingerprints.txt`
-  $ caff -REM `cat ksp-fingerprints.txt`
-  $ caff -RSE `cat ksp-fingerprints.txt`
+  $ caff --no-sign --no-export-old --no-mail "`cat ksp-fingerprints.txt`"
+  $ caff --no-download --no-export-old --no-mail "`cat ksp-fingerprints.txt`"
+  $ caff --no-download --no-sign --no-export-old "`cat ksp-fingerprints.txt`"
 
-* If you have multiple local keys, only send mail once after signing with all.
+* If you have multiple local keys, use -u <mykey1>,<mykey2>.
 
-  caff will send out all previously done signatures in the message. (Of course
-  you have to configure $CONFIG{'keyid'} to contain all your key ids.)
-
-  $ caff -EM -u <mykey1> <other_key>
-  $ caff -RE -u <mykey2> <other_key>
+  $ caff -u <mykey1>,<mykey2> <keyids to sign>
 
 * Use gpg-agent.
 
   See README.gpg-agent.
 
- -- Christoph Berg <cb@df7cb.de>  Sat,  2 Jul 2005 21:22:07 +0200
+* Use gpg-sign-args.
+
+  $CONFIG{'gpg-sign-args'} = "save";
+
+  This automatically saves the key after signing in gpg. The advantage is that
+  you do not have to type "save" for each key. The disadvantage is that you
+  cannot choose which UIDs to sign by answering "no" at the "Really sign?"
+  prompt any more; you will have *not* to send out some mails. (And you have
+  unwanted signatures lingering around in ~/.caff/gnupghome/pubring.gpg.)
 
+ -- Christoph Berg <cb@df7cb.de>  Mon, 25 Jun 2007 10:55:40 +0200