diff --git a/deny.toml b/deny.toml index f446cc193..a86a923b6 100644 --- a/deny.toml +++ b/deny.toml @@ -14,57 +14,7 @@ targets = [ [advisories] yanked = "deny" -ignore = [ - # https://rustsec.org/advisories/RUSTSEC-2023-0071 - # "rsa" crate: Marvin Attack: potential key recovery through timing sidechannel - # - # No patch is yet available, however work is underway to migrate to a fully constant-time implementation. - # So we need to accept this, as of SDP 26.3 we are "only" using the crate to create private + - # public key pairs used by webhooks, such as conversion or mutating webhooks. - # - # https://github.com/RustCrypto/RSA/issues/19 is the tracking issue - "RUSTSEC-2023-0071", - - # https://rustsec.org/advisories/RUSTSEC-2024-0436 - # The "paste" crate is no longer maintained because the owner states that the implementation is - # finished. There are at least two (forked) alternatives which state to be maintained. They'd - # need to be vetted before a potential switch. Additionally, they'd need to be in a maintained - # state for a couple of years to provide any benefit over using "paste". - # - # This crate is only used in a single place in the xtask package inside the declarative - # "write_crd" macro. The impact of vulnerabilities, if any, should be fairly minimal. - # - # See thread: https://users.rust-lang.org/t/paste-alternatives/126787/4 - # - # This can only be removed again if we decide to use a different crate. - "RUSTSEC-2024-0436", - - # https://rustsec.org/advisories/RUSTSEC-2026-0097 - # rand 0.8.5 is unsound when log+thread_rng features are enabled and a custom logger calls rand::rng(). - # - # This version is pulled in transitively via num-bigint-dig -> rsa -> stackable-certs and cannot be - # updated until the upstream rsa crate bumps its rand dependency. - "RUSTSEC-2026-0097", - - # https://rustsec.org/advisories/RUSTSEC-2026-0173 - # The author of `proc-macro-error2` has [confirmed](https://github.com/GnomedDev/proc-macro-error-2/issues/17#issuecomment-4643215473) - # that the crate is no longer maintained and recommends that users migrate away from it. - # - # There currently is no way for us to negate this advisory, because that crate is not used - # directly by us. We need to wait for new versions of oci-spec and getset. See the following - # issue which tracks moving to a newer getset version: https://github.com/youki-dev/oci-spec-rs/issues/340 - # - # proc-macro-error2 v2.0.1 - # └── getset v0.1.6 - # └── oci-spec v0.9.0 - # └── boil v0.2.1 - # - # Alternate crates are: - # - # - https://crates.io/crates/manyhow - # - https://github.com/SergioBenitez/proc-macro2-diagnostics - "RUSTSEC-2026-0173", -] +ignore = [] [bans] multiple-versions = "allow"