> Mmmh, looking at the test I tried to figure out how this is possible. One
> reason I can think of is that the test just checks for gnupg-2.1.16 but not if
> the used libgcrypt supports curve 25519 (which is used for the test keys). Can
> you please post the output of gpg2 (or gpg) --version of the system the tests
> run to either confirm or disregard that theory?
> Or just the version number of libgcrypt, assuming your libgcrypt did not have
> this specially disabled.
Here it is:
gpg (GnuPG) 2.1.18
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
On Wednesday 29 March 2017 12:31:07 Alon Bar-Lev wrote:
> gpg (GnuPG) 2.1.18
> libgcrypt 1.7.6
Ok so that theory is out of the window. But I realized that the tests don't
check for TOFU support in gnupg but just assume it based on the version
number. So I was able reproduce the test failure if I compile gnupg with --
disable-tofu (or if it's compiled without sqlite).
> Thanks for your report,
> Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ > Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
> Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner