-------------------------------
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:
caff and gpg allow you to specify the full fingerprint. This will save you
from having to check the fingerprint yourself. If you have a text file with
- all fingerprints, use that and then run
+ all fingerprints (with all the spaces stripped from them), use that and then
+ run
$ caff <options> `cat ksp-fingerprints.txt`
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 --no-export-old --no-mail -u <mykey1> <other_key>
- $ caff --no-download --no-export-old -u <mykey2> <other_key>
+ $ caff --no-export-old --no-mail -u <mykey1> <keyids to sign>
+ $ caff --no-download --no-export-old -u <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> Wed, 6 Jul 2005 13:46:16 +0200