new testsuite errors with gcrypt 1.5 and gnutls 2.17.1
tmraz at redhat.com
Mon Jul 25 12:51:39 CEST 2011
On Mon, 2011-07-25 at 12:39 +0200, Werner Koch wrote:
> On Mon, 25 Jul 2011 09:41, tmraz at redhat.com said:
> > Hmm... wouldn't it be more proper to make the default MPI format for
> > gcry_sexp_nth_mpi USG? Given the libgcrypt-1.4.x always behaved like
> > this this is strictly said API/ABI break, regardless of what
> > documentation says.
> No, it didn't behaved like this. The case with the leading zeroes is
> more complex that just the GCRMPI_FMT_STD default. It was a bug in
> GnuPG to use the default. Fortunately most users of Libgcrypt didn't
> copied that bug.
I understand that, but what would be broken (that was not broken already
in libgcrypt-1.4.x) if the GCRY_MPI_FMT_USG was declared as default for
gcry_sexp_nth_mpi() ? Is there currently any known use in existing
software that expects the GCRY_MPI_FMT_STD if 0 is specified as format
No matter how far down the wrong road you've gone, turn back.
More information about the Gcrypt-devel