I had this same problem on mcrypt on FreeBSD, which apparently has OpenPGP format as default. I tested it on my Ubuntu Intrepid workstation, I didn't have this problem.... untill I used --openpgp:
MCRYPT_KEY=blaataap mcrypt --openpgp < k.tar >a *** stack smashing detected ***: mcrypt terminated On FreeBSD (mcrypt version 0.9.7.1, libmcrypt 2.5.8) I recompiled mcrypt, and enabled coredumps by disabling SIGSEGV signal handler. The backtrace is: Loaded symbols for /libexec/ld-elf.so.1 #0 0x281d92aa in memcpy () from /lib/libc.so.6 (gdb) bt #0 0x281d92aa in memcpy () from /lib/libc.so.6 #1 0x08052539 in make_ustring (buffer=0xbfbfaae0 #"+�\233/\035�s��\032oI\017", length=22552) at rfc2440.c:78 #2 0x08054036 in encrypted_encode (pt=0x8092000, dek=0x808d080) at #rfc2440.c:811 #3 0x08054b5b in pgp_encrypt_file (infile=0x0, outfile=0x0, pass=0x8085140 #"blaataap") at rfc2440.c:1062 #4 0x0804dc1b in pgp_encrypt_wrap (infile=0x0, outfile=0x0, pass=0x8085140 #"blaataap") at openpgp.c:46 #5 0x0804cc3c in main (argc=5, argv=0xbfbfece4) at mcrypt.c:633 (gdb) It works when using --no-openpgp (this option not listed in the manpage).. I have been looking at the code... I think the problem is earlier in the trace than make_ustring (which seems to be alright). -- attempting to encrypt to openpgp format core dumps https://bugs.launchpad.net/bugs/73885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
