On 2016-04-20 Niko Tyni <nt...@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? [...] Hello Niko, 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 Please take a look at the short thread on libgcrypt-devel for full details. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'