diff options
| author | David Bremner <david@tethera.net> | 2016-09-08 09:03:15 -0300 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2016-09-08 09:08:09 -0300 |
| commit | 7edded2740603eb9cde84f2c7b421026fbac3640 (patch) | |
| tree | 1e966a30461e193647bf370fae12b01f0b9d1298 | |
| parent | 98da3c079a6b42fa36663e7ecae0c8e6f0e01b8f (diff) | |
test/crypto: hard code fingerprint
Originally the intent was to make the test more robust against changing
test keys. It turns out that (unscientifically) gpg --with-colons output
changes more often than our test key. Rather than making the script more
complex, just hard code the fingerprint.
This fixes Debian bug #847013; I expect similar test failures as other
distros adopt gnupg 2.1.15
| -rwxr-xr-x | test/T350-crypto.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/T350-crypto.sh b/test/T350-crypto.sh index 3656cce9..96349fa0 100755 --- a/test/T350-crypto.sh +++ b/test/T350-crypto.sh @@ -25,8 +25,8 @@ add_gnupg_home () ################################################## add_gnupg_home -# get key fingerprint -FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | grep '^fpr:' | cut -d: -f10) +# Change this if we ship a new test key +FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381" test_expect_success 'emacs delivery of signed message' \ 'emacs_fcc_message \ |