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 2139524 - [Rebase] Rebase certmonger to the latest upstream release
Summary: [Rebase] Rebase certmonger to the latest upstream release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: certmonger
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Rob Crittenden
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-02 19:44 UTC by Rob Crittenden
Modified: 2023-05-09 09:01 UTC (History)
3 users (show)

Fixed In Version: certmonger-0.79.17-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:46:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-8967 0 None None None 2022-11-02 19:48:38 UTC
Red Hat Issue Tracker RHELPLAN-138142 0 None None None 2022-11-02 19:48:43 UTC
Red Hat Product Errata RHBA-2023:2322 0 None None None 2023-05-09 07:46:17 UTC

Description Rob Crittenden 2022-11-02 19:44:23 UTC
Rebase certmonger to the latest upstream release

Comment 2 Florence Blanc-Renaud 2022-12-14 08:49:59 UTC
Moving to MODIFIED as the build has already been done with the rebase (certmonger-0.79.17-1.el9)

Comment 5 Michal Polovka 2022-12-21 11:26:00 UTC
# rpm -q certmonger 
certmonger-0.79.17-1.el9.x86_64

# rpm -q --changelog certmonger
* Tue Dec 06 2022 Rob Crittenden <rcritten> - 0.79.17-1
- Update to upstream 0.79.17

* Thu Apr 07 2022 Rob Crittenden <rcritten> - 0.79.14-7
- Disable DSA (#2066439)

* Thu Mar 17 2022 Rob Crittenden <rcritten> - 0.79.14-6
- Certificate format validation when adding the SCEP server's CA
  (#1492112)
- Replace some SHA1 usages with SHA256 in the unit tests

* Thu Oct 07 2021 Rob Crittenden <rcritten> - 0.79.14-5
- Certmonger SCEP renewal should not use old challenges (#1990926)
- Certmonger certificates stuck in NEED_GUIDANCE (#2001082)
- certmonger creates CSRs with invalid DER syntax for X509v3 extensions
  with critical=FALSE (#2012261)

* Tue Sep 28 2021 Rob Crittenden <rcritten> - 0.79.14-4
- Fix FTBFS due to change in OpenSSL 3.0.0-beta2 API (#2008451)

Latest upstream commit present, marking as verified. Automation not needed.

Comment 7 errata-xmlrpc 2023-05-09 07:46:16 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 (certmonger 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/RHBA-2023:2322


Note You need to log in before you can comment on or make changes to this bug.