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.
Description of problem:
It's not possible to create a PKCS#11 token that will support only specific RSA signature methods (e.g. only "RSA-PKCS#1 v1.5" or only "rsassa-pss", without raw RSA).
Additional info:
This is necessary to test fallback mechanism in TLS libraries, as RSA-PSS signatures are mandatory in TLS 1.3, but not all hardware PKCS#11 tokens support them.
(In reply to Kaleem from comment #4)
> Hubert,
>
> How this change can be tested?
Part of the upstream pull request is a test, which is invoked with `make check`. If you want a downstream test for this particular use case, you can start with the upstream configuration file for reference (token.mechanisms is the new configuration option):
https://github.com/opendnssec/SoftHSMv2/pull/455/files#diff-a6a5b67fa56bb9bc79e2bd033854b5f1
When you will have inititialized softhsm2 token, you can use pkcs11-tool to list supported mechanisms of the pkcs11 module.
pkcs11-tool -M --module /path/to/libsofthsm2.so
By default, there will be lots of mechanisms. You can try to remove some by specifying them in the above option prefixed with "-" (as described in manual page, which is also updated in this PR), or specify just limited list, which should be reflected in the list reported in pkcs11-tool.
Comment 6Alexander Bokovoy
2020-04-01 06:28:43 UTC
Sorry, this is RHEL8 bugzilla, mixed up with RHEL7 one.
Comment 7Alexander Bokovoy
2020-04-01 07:11:33 UTC
Will be fixed in idm:DL1 module stream build that includes softhsm-2.6.0-1.el8
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 (Moderate: idm:DL1 and idm:client security, 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/RHSA-2020:4670