Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1233182 +++
+++ The reproducer fails the same at RHEL6's gnupg2-2.0.14-8.el6 +++
Description of problem:
RSA-{E,S} public keys cannot be imported using --import. gpg throws error "no valid user IDs". Using -v gpg says: "unsupported public key algorithm". --list-packets can't handle it either.
Version-Release number of selected component (if applicable):
2.0.22-3.el7
How reproducible:
always
Steps to Reproduce:
1. try to import an RSA-E or RSA-S public key
Actual results:
the key does not get imported
Expected results:
the key gets imported
Additional info:
libgcrypt in RHEL 7 does not support RSA-{E,S}. This has been addressed later in libgcrypt's upstream commit 773e23698218755e9172d2507031a8263c47cc0b. Before that, the issue was addressed in gnupg in upstream commit 30ec869b8c63f1edcc58110ed20b83b0e77248f8.
--- Additional comment from RHEL Product and Program Management on 2015-06-18 13:46:44 CEST ---
Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from Marcel Kolaja on 2015-06-18 13:50:14 CEST ---
[mkolaja@rhel7 tmp]$ gpg -v --import test.asc
Version: BCPG v1.46
gpg: armor header:
gpg: can't handle public key algorithm 3
gpg: can't handle public key algorithm 2
gpg: pub 0s/434D0C5E 2015-02-03 Q32 <q32>
gpg: key 434D0C5E: unsupported public key algorithm on user ID "Q32 <q32>"
gpg: key 434D0C5E: unsupported public key algorithm
gpg: key 434D0C5E: skipped user ID "Q32 <q32>"
gpg: key 434D0C5E: skipped subkey
gpg: key 434D0C5E: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg: w/o user IDs: 1
[mkolaja@rhel7 tmp]$ gpg -v --list-packets test.asc
Version: BCPG v1.46
:public key packet:
version 4, algo 3, created 1422966003, expires 0
unknown algorithm 3
gpg: armor header:
gpg: can't handle public key algorithm 3
:user ID packet: "Q32 <q32>"
:signature packet: algo 1, keyid 8A079917E2858583
version 4, created 1422966003, md5len 0, sigclass 0x13
digest algo 2, begin of digest ac a6
hashed subpkt 2 len 4 (sig created 2015-02-03)
subpkt 16 len 8 (issuer key ID 8A079917E2858583)
data: [1024 bits]
:signature packet: algo 3, keyid 1EF7D599434D0C5E
version 4, created 1422966003, md5len 0, sigclass 0x13
digest algo 2, begin of digest e5 06
hashed subpkt 2 len 4 (sig created 2015-02-03)
critical hashed subpkt 11 len 1 (pref-sym-algos: 9)
hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
subpkt 16 len 8 (issuer key ID 1EF7D599434D0C5E)
unknown algorithm 3
:public sub key packet:
version 4, algo 2, created 1422966003, expires 0
unknown algorithm 2
gpg: can't handle public key algorithm 2
:signature packet: algo 3, keyid 1EF7D599434D0C5E
version 4, created 1422966003, md5len 0, sigclass 0x18
digest algo 2, begin of digest fe a6
hashed subpkt 2 len 4 (sig created 2015-02-03)
critical hashed subpkt 11 len 1 (pref-sym-algos: 9)
hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
subpkt 16 len 8 (issuer key ID 1EF7D599434D0C5E)
unknown algorithm 3
[mkolaja@rhel7 tmp]$
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com