Description of problem:
If CA:TRUE is missing then also we are signing certificates. We can probably have validations added.
Version-Release number of selected component (if applicable):
CS 9.0
How reproducible:
always
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/4d9e33acb23472566ba0ae15d63c5562a0abf7a2
Additional info:
Created a Bugzilla so that it can be used for testing use cases later.
https://bugzilla.redhat.com/show_bug.cgi?id=1330439
Metadata Update from @cipherboy: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1330439 - Custom field type adjusted to None - Custom field version adjusted to None
Duplicate of https://pagure.io/dogtagpki/issue/2309
Metadata Update from @cipherboy: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/3271
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.