Bug#816104: libcrypt-gcrypt-perl: FTBFS against libgcrypt 1.7.0 beta

[Niko Tyni]

Control: tag -1 patch

On Sat, Apr 23, 2016 at 02:55:55PM +0200, Andreas Metzler wrote:
> On 2016-04-20 Niko Tyni <ntyni at debian.org> wrote:
> [...]
> > The failure can be triggered with this:
> 
> >  % perl -MCrypt::GCrypt -e '$c=Crypt::GCrypt->new(type=>"cipher",algorithm=>"aes");$c->start("encrypting"); $c->encrypt("a").$c->finish'
> 
> > which gets a SIGSEGV in libgcrypt. Backtrace below.
> 
> > Adding a $c->setkey('whatever') before calling encrypt() makes it go
> > away. The test isn't trying to do anything meaningful at that point,
> > it's just checking that it gets a warning when not calling $c->finish()
> > or something like that. Later tests of actual encrypting pass.
> 
> > Is this something to be fixed on the libgcrypt side?

> I have forwarded this upstream
> <http://article.gmane.org/gmane.comp.encryption.gpg.libgcrypt.devel/4487>
> and got a quick response, whichcan be summed up in short with:
> 1. encryption without setkey must not be used.
> 2. gcrypt should throw an error instead of a segfault

Thanks! The attached trivial patch fixes the test failure in
libcrypt-gcrypt-perl by calling setkey() first. I've verified it works
with both libgcrypt 1.6.5 and 1.7.0.
-- 
Niko Tyni   ntyni at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-an-encryption-key-in-the-test-suite.patch
Type: text/x-diff
Size: 1083 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20160423/3693cec3/attachment.patch>