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:
As part of the Common Criteria evaluation, our evaluation testing lab, Gossamer, reported that the instruction we give in the guidance on using certutil does not meet the requirement.
The requirement is to NOT allow import of a cert until verified.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. follow latest version of CC guidance Planning guide
Chapter 13. Managing Certificate/Key Crypto Token
2. import using "certutil -A ..."
3. verify using "certutil -V ..."
Actual results:
The instruction itself breaks the requirement of "no import until verification".
Expected results:
instruction should be "verify and then import"
Additional info:
further discussion with Gossamer and Bob Relyea, we decided to write a shell script wrapper for certutil and adopt the two-token approach to achieve "verify first; import after".
Commits:
master: 8e22d591c41923a5291db486d2f697bd3d87d2cb
10.6: 0d4e2ca49f0f2496f9201a143cb05eea36c8ad7e
10.5: a187cccc269968e310d97eafc99771d2cd5b366e
Add validate-then-import certificate utility
The NSS utility certutil requires certificates to be imported
(`certutil -A`) prior to validating their signatures and usage
(`certutil -V -e`). PKICertImport avoids this pitfall by handling both
import and validation in the same step, so if the validation fails, the
certificate is removed. This ensures it is not accidentally used before
it is verified.
Signed-off-by: Alexander Scheel <ascheel>
master: f95e5fb5240e2c51caca28a92d5822dc3ee27408
10.6: c4168e0332f87931128a8fddc0398612333855c6
10.5: b85472cd6c33828c5d9bd7248291515687b5ca1f
Add PKICertImport to pki
Signed-off-by: Alexander Scheel <ascheel>
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://access.redhat.com/errata/RHBA-2019:2228