Christian HesseGnuPG homedir is generated on the fly and keys are imported from armored key file. Make commet match available key info and new key generation procedure.
Signed-off-by: Christian Hesse <mail@eworm.de> --- t/lib-gpg.sh | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
Show changes to t/lib-gpg.sh +13 −3
diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh index 33de402..d88da29 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 <committer@example.com> + # Available key info: + # * Type DSA and Elgamal, size 2048 bits, no expiration date, + # name and email: C O Mitter <committer@example.com> + # * Type RSA, size 2048 bits, no expiration date, + # name and email: Eris Discordia <discord@example.net> # 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.2.0
