The issue was with corrupt secring.gpg. Solved by using gpg --no-default-keyring --keyring ./fixed-pubring.gpg --secret-keyring ./fixed-secring.gpg --import /path/to/your/broken/secring.gpg
Thanks everyone. On Mon, Aug 19, 2013 at 7:49 AM, David Shaw <ds...@jabberwocky.com> wrote: > On Aug 18, 2013, at 11:45 AM, ashish tiwari <ashishtewariash...@gmail.com> > wrote: > > > echo test123|/usr/local/bin/gpg --no-tty --passphrase-fd 0 -o > /apploatr/.gnupg/ab.pgp --debug-level advanced --log-file a.log --sign > --encrypt -r nkumar /apploatr/.gnupg/test.txt > > > > gpg: Ohhhh jeeee: ... this is a bug (getkey.c:2696:lookup) > > secmem usage: 1632/1632 bytes in 3/3 blocks of pool 1632/32768 > > ksh: 41382116 IOT/Abort trap > > I think this is a corrupt secret keyring. Regardless of the issue of > "-sign" vs "--sign", an abort like that shouldn't happen. I don't know > what version of GnuPG this is, but the only BUG() call in the lookup > function is one that fires if the packet it sees in the secret keyring is > not a secret key. > > David > >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
