Red Hat Bugzilla – Bug 1078962
gpg --verify coredumps when verifying a signature with RIPEMD160 digest in FIPS mode
Last modified: 2016-11-03 21:30:24 EDT
+++ This bug was initially created as a clone of Bug #1078957 +++ Description of problem: # rpm -q gnupg2 gnupg2-2.0.22-3.el7.x86_64 # ls -l /etc/gcrypt/fips_enabled -rw-r--r--. 1 root root 0 Mar 20 16:41 /etc/gcrypt/fips_enabled # gpg --list-packets < signature :signature packet: algo 17, keyid 9E729DAF06947932 version 4, created 1269352544, md5len 0, sigclass 0x00 digest algo 3, begin of digest ac be hashed subpkt 2 len 4 (sig created 2010-03-23) subpkt 16 len 8 (issuer key ID 9E729DAF06947932) data: [160 bits] data: [160 bits] # gpg -v --verify --keyring /etc/webapp-keyring.gpg signature Version: Crypt::OpenPGP 1.03 DBG: md_enable: algorithm 3 not available gpg: armor header: gpg: Ohhhh jeeee: ... this is a bug (mainproc.c:2166:proc_tree) Aborted Version-Release number of selected component (if applicable): gnupg2-2.0.22-3.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. RHEL-7 in FIPS mode 2. Try to verify a signature which contains RIPEMD160 digest Actual results: Above error. Expected results: More meaningful error message without a coredump. Additional info: N/A
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2238.html