tests/libtest: Record long GPG key IDs and fingerprints
Use long GPG key IDs as it's safer and matches the format used by gpg and gpgme. Add the associated fingerprints since these are needed by gpg when manipulating keys.
This commit is contained in:
parent
c54a3b5daa
commit
7f04c5d764
|
|
@ -78,9 +78,12 @@ unset TAR_OPTIONS
|
|||
# easily clean up.
|
||||
export OSTREE_SYSROOT_DEBUG=mutable-deployments
|
||||
|
||||
export TEST_GPG_KEYID_1="472CDAFA"
|
||||
export TEST_GPG_KEYID_2="CA950D41"
|
||||
export TEST_GPG_KEYID_3="DF444D67"
|
||||
export TEST_GPG_KEYID_1="7FCA23D8472CDAFA"
|
||||
export TEST_GPG_KEYFPR_1="5E65DE75AB1C501862D476347FCA23D8472CDAFA"
|
||||
export TEST_GPG_KEYID_2="D8228CFECA950D41"
|
||||
export TEST_GPG_KEYFPR_2="7B3B1020D74479687FDB2273D8228CFECA950D41"
|
||||
export TEST_GPG_KEYID_3="0D15FAE7DF444D67"
|
||||
export TEST_GPG_KEYFPR_3="7D29CF060B8269CDF63BFBDD0D15FAE7DF444D67"
|
||||
|
||||
# GPG when creating signatures demands a writable
|
||||
# homedir in order to create lockfiles. Work around
|
||||
|
|
|
|||
Loading…
Reference in New Issue