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 1532867 - Inconsistent key ID encoding (RHEL)
Summary: Inconsistent key ID encoding (RHEL)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks: 1546933
TreeView+ depends on / blocked
 
Reported: 2018-01-09 22:53 UTC by Matthew Harmsen
Modified: 2020-10-04 21:38 UTC (History)
2 users (show)

Fixed In Version: pki-core-10.5.1-9.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1546933 (view as bug list)
Environment:
Last Closed: 2018-04-10 17:02:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 3002 0 None None None 2020-10-04 21:38:57 UTC
Red Hat Product Errata RHBA-2018:0925 0 None None None 2018-04-10 17:03:37 UTC

Description Matthew Harmsen 2018-01-09 22:53:47 UTC 
Key IDs are displayed as unsigned hex numbers by certutil:

    $ certutil -K -d /var/lib/pki/pki-tomcat/alias/ -f password.txt
    certutil: Checking token "NSS Certificate DB" in slot "NSS User Private Key and Certificate Services"
    < 0> rsa      7c2dd8cd2213494ab6e26e70fde332669f17f913   ca_ocsp_signing
    < 1> rsa      e91f694a9e7c753cd7aa533cf5f6195d26523ee0   NSS Certificate DB:sslserver
    < 2> rsa      446ed35d7e811e7f73d0d1f220afc60083deba74   ca_signing
    < 3> rsa      34488253ad5443552b89c4087b4e36e6d212ba17   subsystem
    < 4> rsa      b60333e92c6d9643b6e41407fa1557e54a442e35   ca_audit_signing

However, the key IDs are stored as signed hex numbers in CS.cfg:

    cloning.audit_signing.privkey.id=-49fccc16d39269bc491bebf805eaa81ab5bbd1cb
    cloning.ocsp_signing.privkey.id=7c2dd8cd2213494ab6e26e70fde332669f17f913
    cloning.signing.privkey.id=446ed35d7e811e7f73d0d1f220afc60083deba74
    cloning.subsystem.privkey.id=34488253ad5443552b89c4087b4e36e6d212ba17

Also, PKI is always treating the key ID as signed hex numbers in various locations.

Depending on the value, sometimes they may not match and may lead to confusions or other problems.

To avoid potential problems, they should be treated consistently as unsigned hex numbers.
Comment 2 Matthew Harmsen 2018-01-18 19:53:57 UTC 
Per PKI Team Meeting of 20180118 moving to RHEL 7.6.

NOTE:  As we cannot control the creation of IDs, we request that anyone
       encountering this bug provide a db with an offending key starting
       with a '0' so that we may adequately fix this issue.
Comment 6 Endi Sukma Dewata 2018-02-14 01:50:01 UTC 
Fixed in upstream 10.5 branch:

* https://github.com/dogtagpki/pki/commit/431ad0ec9f6f8188c1d240ed60966d53a4c6982b
* https://github.com/dogtagpki/pki/commit/313d763273f3a03f1f40b559d6428c182bea0479
* https://github.com/dogtagpki/pki/commit/e3287c2f0de27a3c3a8d2d62253077fe4663a5c0
* https://github.com/dogtagpki/pki/commit/c46f53ff6f2fb398600c59410b2afe14fed9dbfa
* https://github.com/dogtagpki/pki/commit/d9969e2c2c5895056d4ecdb04718d5a4473c297d
Comment 8 Roshni 2018-02-22 19:48:55 UTC 
[root@nocp1 ~]# rpm -qi pki-ca
Name        : pki-ca
Version     : 10.5.1
Release     : 9.el7
Architecture: noarch
Install Date: Tue 20 Feb 2018 01:41:57 PM EST
Group       : System Environment/Daemons
Size        : 2359944
License     : GPLv2
Signature   : (none)
Source RPM  : pki-core-10.5.1-9.el7.src.rpm
Build Date  : Mon 19 Feb 2018 11:31:00 PM EST
Build Host  : ppc-034.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://pki.fedoraproject.org/
Summary     : Certificate System - Certificate Authority

Performed the following sanity tests:

1. Smartcard token enrollment with server side key generation.
2. Key recovery using external registration.
Comment 10 errata-xmlrpc 2018-04-10 17:02:54 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://access.redhat.com/errata/RHBA-2018:0925
Note You need to log in before you can comment on or make changes to this bug.