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.

Bug 1150645

Summary: Importing an RSA private key fails if p < q [rhel-7]
Product: Red Hat Enterprise Linux 7 Reporter: Elio Maldonado Batiz <emaldona>
Component: nss-softoknAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED ERRATA QA Contact: Alicja Kario <hkario>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: amarecek, hkario, kengert, ksrot, rrelyea, sforsber
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nss-softokn-3.16.2-7.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1167426 1167427 (view as bug list) Environment:
Last Closed: 2015-03-05 08:28:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1165525    
Bug Blocks: 1167426, 1167427    
Attachments:
Description Flags
Change RSA_PrivateKeyCheck to not require p > q rrelyea: review+

Description Elio Maldonado Batiz 2014-10-08 15:03:09 UTC
Description of problem: This problem was reprted upstream. For the original report see https://bugzilla.mozilla.org/show_bug.cgi?id=1049435#c0


Version-Release number of selected component (if applicable):

How reproducible: see above link

Steps to Reproduce: link anove

Actual results:
Following message will appear in dialog:
  The PKCS #12 operation failed for unknown reasons.
On the other hand,
* "openssl pkcs12" can extract key and certificates.
* "openssl verify" can verify signature in EE certificate.


Expected results:
Key and certificates should be imported.

Additional info:

From https://bugzilla.mozilla.org/show_bug.cgi?id=1049435#c42

The NSS change that broke this was in NSS 3.16.2. See
bug 1021102 and the two bugs named in bug 1021102 comment 0.
At that time I thought p > q was required, and any
incompatibility would be discovered quickly during testing
of mozilla-central nightly builds.

Comment 1 Elio Maldonado Batiz 2014-10-08 15:05:33 UTC
Created attachment 945050 [details]
Change RSA_PrivateKeyCheck to not require p > q

patch applied upstream https://hg.mozilla.org/projects/nss/rev/358730f7261d

Comment 2 Kai Engert (:kaie) (inactive account) 2014-10-09 20:33:07 UTC
*** Bug 1146592 has been marked as a duplicate of this bug. ***

Comment 20 errata-xmlrpc 2015-03-05 08:28:38 UTC
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-2015-0364.html