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 1710105 - JSS: add RSA PSS support
Summary: JSS: add RSA PSS support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jss
Version: 7.9
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jack Magne
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks: 1824939
TreeView+ depends on / blocked
 
Reported: 2019-05-14 21:32 UTC by Christina Fu
Modified: 2020-09-29 20:00 UTC (History)
5 users (show)

Fixed In Version: jss-4.4.9-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1824939 (view as bug list)
Environment:
Last Closed: 2020-09-29 20:00:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3938 0 None None None 2020-09-29 20:00:43 UTC

Description Christina Fu 2019-05-14 21:32:23 UTC
Description of problem:

It was discovered that Thales HSM SW12.50 when in FIPS mode does not allow PKCS1 RSA signing.  Instead, RSA PSS (Probabilistic Signature Scheme) is required.

It is important that we support both mechanisms, as not all crypto modules support PSS.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Jack Magne 2019-09-06 01:00:02 UTC
Moving to 7.9 to have time to finish this feature more completely.

Comment 4 Jack Magne 2020-03-29 19:22:21 UTC
Patch reviewed and checked in:


* v4.4.x    e1ee07a [ahead 1] JSS RSA-PSS support first cut.

commit e1ee07a3c19cd15d7dab1dedf383128a2b83b925
Author: root <root.lab.eng.rdu2.redhat.com>
Date:   Wed Dec 11 19:56:22 2019 -0500

    JSS RSA-PSS support first cut.
    
    Provide support for the various SHAxxxwithRSAPSS algorithms.
    
    Supprt for 256, 384, and 512 variants included.
    Included test case for SHA256withRSA/PSS.
    
    This fix also requires a corresponding fix to the pki server in
    order to exercise this functionality in the context of a pki
    ca server.
    
    Add some review suggestions.
    More review suggestions.

Comment 12 errata-xmlrpc 2020-09-29 20:00:37 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 (jss bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:3938


Note You need to log in before you can comment on or make changes to this bug.