v/0.102.4
RevocationOptionsBuilder
now offers awith_expiration_policy()
fn for setting anExpirationPolicy
that will be used to determine how to handle CRLs that have aNextUpdate
value 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::CrlExpired
error.EndEntityCert
now offers asubject_public_key_info()
fn for accessing the RFC 5280pki_types::SubjectPublicKeyInfoDer
.
What's Changed
- build(deps): bump serde from 1.0.198 to 1.0.199 in the crates-io group by @dependabot in #250
- benches: ignore clippy::incompatible_msrv by @cpu in #251
- build(deps): bump the crates-io group with 3 updates by @dependabot in #252
- Add SubjectPublicKeyInfo methods for cert::Cert by @lvkv in #253
- build(deps): bump the crates-io group across 1 directory with 2 updates by @dependabot in #255
- Add support for enforcing CRL expiration using nextUpdate field by @jasperpatterson in #227
- Cargo: v0.102.3 -> v0.102.4 by @cpu in #256
New Contributors
Full Changelog: v/0.102.3...v/0.102.4