New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #28714 - Limit the certificate end date to late 2049 #8507
Conversation
Subscription-manager (python-rhsm) can't read the certificate with end date deyond 2049 year correctly. It will read the date as 1949 year which causing the pool of the custom products not accessible.
|
Can one of the admins verify this patch? |
|
Issues: #28714 |
|
ok to test |
|
This fails |
| # End it 100 years from now | ||
| end_date ||= start_date + 10_950.days | ||
|
|
||
| # Subscription-manager (python-rhsm) can't read the certificate with end date deyond |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Subscription-manager (python-rhsm) can't read the certificate with end date deyond | |
| # Subscription-manager (python-rhsm) can't read the certificate with end date beyond |
|
|
||
| # Subscription-manager (python-rhsm) can't read the certificate with end date deyond | ||
| # 2049 year correctly. Refer the links below for more details: | ||
| # https://bugzilla.redhat.com/show_bug.cgi?id=1789654 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the comments are private, such as linking to RFC 5280 that states:
CAs conforming to this profile MUST always encode certificate validity dates through the year 2049 as UTCTime; certificate validity dates in 2050 or later MUST be encoded as GeneralizedTime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i can make that comment not-private
| # 2049 year correctly. Refer the links below for more details: | ||
| # https://bugzilla.redhat.com/show_bug.cgi?id=1789654 | ||
| # https://github.com/candlepin/candlepin/blob/5b87865f304555c112982af4fbc83a1c463d37b2 | ||
| # /server/src/main/java/org/candlepin/model/UeberCertificateGenerator.java#L247 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how useful it is to split a URL over multiple lines
Subscription-manager (python-rhsm) can't read the certificate
with end date deyond 2049 year correctly. It will read the date
as 1949 year which causing the pool of the custom products not
accessible.