-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Update soon to be expired crl #2417
Conversation
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.
LGTM
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.
Thanks for catching the server1_all
issue. Still looks good to me.
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.
@RonEld Have you checked other test CRLs for the expiration time?
@hanno-arm Yes. All the other CRLs we have, the soonest year they expire is 2024. We have other CRLs that expired at 2011, so since we didn't get any errors sine, they are probably not used in our tests, and we require some house cleaning for certificates and crls not used in tests. |
Or perhaps the expired CRLs are used in tests that actually need the CRL to be expired? |
perhaps. I have noticed that:
and that
I haven't checked other certificates. Anyway, this should be handled in a different PR, and maintained regularly. |
@RonEld I'd prefer those CRTs to be regenerated (and their build-instructions to be rewritten) so that they don't expire in the next 3 years. Now you/we are into the issue and it's easy to fix along the way, while waiting for another report to come up in a year's time or so and triaging and fixing it again will be more work. |
In addition to what Hanno wrote, our LTS branches are supported for 3 years, so I think it would make sense for us to always ensure |
@hanno-arm @mpg I agree that we should have a test that will ensure |
@RonEld I'm not sure this is an entirely different task - this PR is about making tests pass in 1 year, so just changing the numeric value from 1 to 3 hardly changes the nature of the task IMO. (The larger work you suggest in your email would indeed be a pretty different task.) However, if you really to handle the two remaining certs necessary to pass in 3 years in this PR, I'll still approve this PR as it stands in the interest of unblocking it, as it already brings a valuable improvement that I don't want to block by requesting more of the same. |
I am working on making the tests pass in three years. however htis is more than just changing two certificates |
@RonEld Why is that more than just changing the two certificates you mentioned in this earlier message? How much more? I based my previous comment on the assumption that it would be just changing two certs, so if it's much more that than I could change my mind. |
The task for making it pass in three years include:
As mentioned, I am currently working on this, probably be ready by end of day |
@hanno-arm @mpg I have updated the certificates and corresponding test data files to make our tests pass 3 years ahead. I ran the following tests to verify:
A few notes:
Please review |
Note: I think it's worth fixing #822 as part of this PR |
@k-stachowiak @AndrzejKurek I amended the commit "Update certificates to expire in 2029 " to fix CI failure.
Please review |
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.
LGTM
This PR and its backports have been fully reviewed and approved. Removing the "needs backports" label cc @Patater |
Hi, I'm wondering what is missing here for this to get merged? The 2019-11-25 expiry of the crl is not that far away. |
collides with
|
Update crl.pem, as it will expire on November 25 2019. Resolves Mbed-TLS#2357.
Update certificates that expire on 2021, to prolong their validity, to make tests pass three years ahead.
@k-stachowiak @AndrzejKurek I have rebased to resolve conflicts |
Add support for `MBEDTLS_SHA_224` and `MBEDTLS_SHA_384` in `cert_write`, to support generating such certificates in `tests/data_files/Makefile`.
This PR is fully reviewed, so removing the "needs backports" label |
Description
Update crl.pem, as it will expire on November 25 2019.
Resolves #2357.
Status
READY
Requires Backporting
Yes
As this crl will be expired on the LTS branch, which will still be supported on November 25 2019, need to backport as well.
Todos