From 6fb5df6c77070f7cea5391572003ecfea3235650 Mon Sep 17 00:00:00 2001 From: Christian Hesse Date: Tue, 16 Dec 2014 09:40:05 +0100 Subject: [PATCH] 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 Signed-off-by: Junio C Hamano --- t/lib-gpg.sh | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh index 33de4020f6..d88da29f77 100755 --- a/t/lib-gpg.sh +++ b/t/lib-gpg.sh @@ -12,10 +12,20 @@ else say "Your version of gpg (1.0.6) is too buggy for testing" ;; *) - # key generation info: gpg --homedir t/lib-gpg --gen-key - # Type DSA and Elgamal, size 2048 bits, no expiration date. - # Name and email: C O Mitter + # Available key info: + # * Type DSA and Elgamal, size 2048 bits, no expiration date, + # name and email: C O Mitter + # * Type RSA, size 2048 bits, no expiration date, + # name and email: Eris Discordia # No password given, to enable non-interactive operation. + # To generate new key: + # gpg --homedir /tmp/gpghome --gen-key + # To write armored exported key to keyring: + # gpg --homedir /tmp/gpghome --export-secret-keys \ + # --armor 0xDEADBEEF >> lib-gpg/keyring.gpg + # To export ownertrust: + # gpg --homedir /tmp/gpghome --export-ownertrust \ + # > lib-gpg/ownertrust mkdir ./gpghome && chmod 0700 ./gpghome && GNUPGHOME="$(pwd)/gpghome" && -- 2.11.4.GIT