Use timezone-aware timestamps on x509.Certificate
if possible
#399
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cryptography issues a deprecation warning when timezone-unaware datetime properties are accessed on
x509.Certificate
instances. For example:Since version 42.0.0 there are timezone-aware alternatives that should be used instead. In this PR usages of naive datetime properties
x509.Certificate.not_valid_after
andx509.Certificate.not_valid_before
are replaced with timezone-aware propertiesx509.Certificate.not_valid_after_utc
andx509.Certificate.not_valid_before_utc
respectively.