-
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
Backport 2.16: Always revoke certificate on CRL #3562
Backport 2.16: Always revoke certificate on CRL #3562
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.
One change is needed for 2.16 and 2.7. Other than that looks good to me.
tests/scripts/all.sh
Outdated
@@ -1094,6 +1094,16 @@ component_test_null_entropy () { | |||
make test | |||
} | |||
|
|||
component_test_no_date_time () { | |||
msg "build: default config without MBEDTLS_HAVE_TIME_DATE" | |||
scripts/config.py unset MBEDTLS_HAVE_TIME_DATE |
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.
config.py
needs to be config.pl
in 2.16 and 2.7.
0e75c4b
to
2789382
Compare
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.
Looks good to me.
RFC5280 does not state that the `revocationDate` should be checked. In addition, when no time source is available (i.e., when MBEDTLS_HAVE_TIME_DATE is not defined), `mbedtls_x509_time_is_past` always returns 0. This results in the CRL not being checked at all. https://tools.ietf.org/html/rfc5280 Signed-off-by: Raoul Strackx <[email protected]>
75475d8
2789382
to
75475d8
Compare
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, thanks for resolving the conflicts.
Description
backport of #3433
RFC5280 does not state that the
revocationDate
should be checked.In addition, when no time source is available (i.e., when MBEDTLS_HAVE_TIME_DATE is not defined),
mbedtls_x509_time_is_past
always returns 0. This results in the CRL not being checked at all.https://tools.ietf.org/html/rfc5280
Status
READY
Migrations
If there is any API change, what's the incentive and logic for it.
NO