Cargo: v0.102.3 -> v0.102.4 #256
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
djc
approved these changes
May 16, 2024
ctz
approved these changes
May 16, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed Release Notes
RevocationOptionsBuildernow offers awith_expiration_policy()fn for setting anExpirationPolicythat will be used to determine how to handle CRLs that have aNextUpdatevalue in the past. The default behaviour is to ignore theNextUpdate. Users wishing to use a stricter policy can do so by specifyingExpirationPolicy::Enforce. Revocation checking against an expired CRL will then produce anError::CrlExpirederror.EndEntityCertnow offers asubject_public_key_info()fn for accessing the RFC 5280pki_types::SubjectPublicKeyInfoDer.