Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

gpg2 signing failure, possibly upstream GLIBC bug

Justin WarwickOct 21 2021 — edited Oct 21 2021

Using GnuPG bundled with Solaris 11.3, most of the keyring setup steps are successful, but when I attempted to sign files or keys, I am unable to supply passphrase because it immediately fails with a GLib warning. Excerpt from terminal:
$ gpg2 --version
gpg (GnuPG) 2.0.30
libgcrypt 1.7.9
...

$ gpg2 --sign --armor msg.txt
Warning: using insecure memory!

You need a passphrase to unlock the secret key for
user: "ABC (Dept) <xyz@abc.com>"
4096-bit RSA key, ID C63B215F, created 2021-09-21

(process:4460): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported
Warning: using insecure memory!
gpg-agent[4459]: command get_passphrase failed: Operation cancelled
gpg: cancelled by user
gpg: no default secret key: Operation cancelled
gpg: signing failed: Operation cancelled

Would be grateful for any advice or known solutions.

Comments
Post Details
Added on Oct 21 2021
2 comments
291 views