Skip to content

fix: resolve security-audit rand unsound error (exit 0) #668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eval-exec wants to merge 1 commit into
base: develop
Choose a base branch
from
+7 −1
Open

fix: resolve security-audit rand unsound error (exit 0) #668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion deny.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,13 @@ feature-depth = 1
ignore = [
"RUSTSEC-2021-0145",
"RUSTSEC-2024-0421", # https://rustsec.org/advisories/RUSTSEC-2024-0421
"RUSTSEC-2026-0009" # CVE: RFC2822 parser stack recursion in time 0.3.41
"RUSTSEC-2026-0009", # CVE: RFC2822 parser stack recursion in time 0.3.41
# RUSTSEC-2026-0097: rand 0.7.3 unsoundness requires calling
# rand::thread_rng() from inside a custom log::Log implementation while
# trace-level logging is active. ckb-cli uses rand only in normal code
# paths (keystore salt generation, mock tx helper), never in a logger.
# Cannot semver-bump rand due to ckb-vm / jsonrpc-pubsub dep constraints.
"RUSTSEC-2026-0097",
#"RUSTSEC-0000-0000",
#{ id = "RUSTSEC-0000-0000", reason = "you can specify a reason the advisory is ignored" },
#"a-crate-that-is-yanked@0.1.1", # you can also ignore yanked crate versions if you wish
Expand Down
Loading