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:

When using the --lifetime commandline argument of sscg, 20 extra minutes gets added for each day.  So a certificate issued with a lifetime of 1 day, for example, will be valid for 1 day and 20 minutes.

This is particularly problematic when trying to issue certificates which expire in approximately a year and a month (, ~395 days which is the modern limit) because you end up issuing a certificate with a validity of ~400 days, which is over the limit, leading to rejection by browsers.


Version-Release number of selected component (if applicable):

3.0


How reproducible:

100%


Steps to Reproduce:
1. sscg --lifetime 365
2. openssl x509 -enddate -noout < service.pem


Actual results/Expected results:

Notice that you don't get a certificate for today's date a year later, but one a few days after that.

For example, running that just now, I'd expect to see Oct 27 2021 (today, plus one year), but I get Nov 1 instead.


Additional info:

This bug has been reported upstream and the fix has been merged: https://github.com/sgallagher/sscg/pull/28

Patch exists upstream as https://github.com/sgallagher/sscg/commit/68c9ce446f325591e1c32cab88b2f0dd802eab84

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 (new packages: sscg), 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-2022:2432