dogtagpki

#2309 Installation: sanity check externally-signed CA cert
Closed: migrated by dmoluguw. Opened by gkapoor.

Closed: migrated
Reopen Issue

Update (ftweedal): we should check externally signed CA certs to ensure:

  1. BasicConstraints with CA:True
  2. If not self-signed, Authority Key Identifier extension present
  3. Subject key identifier extension present
  4. Subject DN is non-empty
  5. Key Usage extension present, with appropriate values

If CA:TRUE is missing then also we are signing certificates.
We can probably have validations added.

Steps to Reproduce:

1.Sign externalCA using openssl.
2.Don't use CA:TRUE flag.
3.Make sure when we signed CA the new externalCA signed doesn't have CA:TRUE
set.

Actual results:

without CA:TRUE set ,we are able to sign certificates.

Expected results:

CA:TRUE must be checked for validation.  Inevitably, some software
forgets to do that:
https://github.com/openssl/openssl/commit/4d9e33acb23472566ba0ae15d63c5562a0abf
7a2

Additional info:

Created a Bugzilla so that it can be used for testing use cases later.

Per Offline Triage of 11/30/2016-12/01/2016: 10.4 - minor

Metadata Update from @gkapoor:
- Issue set to the milestone: 10.4

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: FUTURE (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: minor)

 
09:12 < ftweedal> it's actually a pretty easy one do to if we do it in pkispawn (use python-cryptography)
09:13 < ftweedal> if we make it a library function in the pki Py libs we can use it from IPA too instead of duplicating the logic

Metadata Update from @ftweedal:
- Issue assigned to ftweedal

Bringing milestone forward to 10.6, which is what #2864 was triaged to
(2864 was closed as a duplicate of this ticket).

Metadata Update from @ftweedal:
- Issue set to the milestone: 10.6 (was: FUTURE)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1330439, https://bugzilla.redhat.com/show_bug.cgi?id=1516118 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1330439)

Per 10.5.x/10.6 Triage: 10.6

Per 10.5.x/10.6 Triage: 10.6

alee: seems to be a useful functionality that was also help with IPA installs

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2429

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
Normal
None
None
None
None
None
defect
General
QE
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.