I'm using the rustls-acme crate in arb, where I encountered a security alert (discussed here) due to the version of the time crate that the chrono crate was using. I fixed it in arb, but the issue persisted since rustls-acme also uses chrono, so I made this small change to the Cargo.toml file to fix it. I've tested everything and am confident it's the correct fix, until chrono is able to release a version that they plan on removing the time dependency from entirely.
I'm using a patched version of rustls-acme for arb in the meantime (which if looked at, please ignore the formatting changes that were required by my workflow), that I'd prefer to remove if this change can be merged into the rustls-acme crate.
I'm using the
rustls-acme
crate in arb, where I encountered a security alert (discussed here) due to the version of thetime
crate that thechrono
crate was using. I fixed it inarb
, but the issue persisted sincerustls-acme
also useschrono
, so I made this small change to theCargo.toml
file to fix it. I've tested everything and am confident it's the correct fix, untilchrono
is able to release a version that they plan on removing thetime
dependency from entirely.I'm using a patched version of
rustls-acme
forarb
in the meantime (which if looked at, please ignore the formatting changes that were required by my workflow), that I'd prefer to remove if this change can be merged into therustls-acme
crate.