tests: make comment on GPG keyring match the code
GnuPG homedir is generated on the fly and keys are imported from armored key file. Make comment match available key info and new key generation procedure. Signed-off-by: Christian Hesse <mail@eworm.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Christian Hesse committed
Dec 16, 2014 at 09:40 UTC
6fb5df6c77070f7cea5391572003ecfea3235650
1 file changed
+13
-3
t/lib-gpg.sh
+13
-3
@@ -12,10 +12,20 @@ else
12
say "Your version of gpg (1.0.6) is too buggy for testing"
13
;;
14
*)
15
- # key generation info: gpg --homedir t/lib-gpg --gen-key
16
- # Type DSA and Elgamal, size 2048 bits, no expiration date.
17
- # Name and email: C O Mitter <committer@example.com>
15
+ # Available key info:
16
+ # * Type DSA and Elgamal, size 2048 bits, no expiration date,
17
+ # name and email: C O Mitter <committer@example.com>
18
+ # * Type RSA, size 2048 bits, no expiration date,
19
+ # name and email: Eris Discordia <discord@example.net>
20
# No password given, to enable non-interactive operation.
21
+ # To generate new key:
22
+ # gpg --homedir /tmp/gpghome --gen-key
23
+ # To write armored exported key to keyring:
24
+ # gpg --homedir /tmp/gpghome --export-secret-keys \
25
+ # --armor 0xDEADBEEF >> lib-gpg/keyring.gpg
26
+ # To export ownertrust:
27
+ # gpg --homedir /tmp/gpghome --export-ownertrust \
28
+ # > lib-gpg/ownertrust
29
mkdir ./gpghome &&
30
chmod 0700 ./gpghome &&
31
GNUPGHOME="$(pwd)/gpghome" &&