Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 623494 - CRL cert "next update time" seems to be hardcoded for 24hr
CRL cert "next update time" seems to be hardcoded for 24hr
Product: Candlepin
Classification: Community
Component: candlepin (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dmitri Dolguikh
wes hayutin
Depends On:
  Show dependency treegraph
Reported: 2010-08-11 18:39 EDT by wes hayutin
Modified: 2015-05-14 11:23 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-21 11:29:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description wes hayutin 2010-08-11 18:39:04 EDT
pinsetter.org.fedoraproject.candlepin.pinsetter.tasks.CertificateRevocationListTask.schedule = 0 0/3 * * * ?

Certificate Revocation List (CRL):
        Version 2 (0x1)
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: /CN=
        Last Update: Aug 11 22:33:00 2010 GMT
        Next Update: Aug 12 22:33:00 2010 GMT
        CRL extensions:
            X509v3 Authority Key Identifier: 

            X509v3 CRL Number: 

Shouldnt the "Next Update:" reflect the actual setting in candlepin.conf?
Not sure if this is by design, but I wanted to double check and open a bug.
Comment 1 Dmitri Dolguikh 2010-09-21 11:29:29 EDT
From rfc 3280:  Next Update

   This field indicates the date by which the next CRL will be issued.
   The next CRL could be issued before the indicated date, but it will
   not be issued any later than the indicated date.  CRL issuers SHOULD
   issue CRLs with a nextUpdate time equal to or later than all previous
   CRLs.  nextUpdate may be encoded as UTCTime or GeneralizedTime.

The above behaviour is not a bug according to RFC.

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