chore: hide warnings for additional known advisories (#3170)
This commit is contained in:
parent
eb203ebe95
commit
d5a5ddf826
|
@ -2,8 +2,17 @@
|
|||
ignore = [
|
||||
# difference is unmaintained
|
||||
# Only used in test code
|
||||
# Tracked in #2835
|
||||
"RUSTSEC-2020-0095",
|
||||
# Out-of-bounds write in nix::unistd::getgrouplist
|
||||
# Tracked in #3140
|
||||
"RUSTSEC-2021-0119"
|
||||
"RUSTSEC-2021-0119",
|
||||
# Potential segfault in the time crate
|
||||
# chrono dependency, but vulnerable function is never called
|
||||
# Tacked in #3163
|
||||
"RUSTSEC-2020-0071",
|
||||
# chrono: Potential segfault in localtime_r invocations
|
||||
# starship avoids setting any environment variables to avoid this issue
|
||||
# Tracked in #3166
|
||||
"RUSTSEC-2020-0159",
|
||||
]
|
|
@ -1,2 +1,6 @@
|
|||
# std::process::Command::new may inadvertly run executables from the current working directory
|
||||
disallowed-methods = ["std::process::Command::new"]
|
||||
disallowed-methods = [
|
||||
# std::process::Command::new may inadvertly run executables from the current working directory
|
||||
"std::process::Command::new",
|
||||
# Setting environment variables can cause issues with non-rust code
|
||||
"std::env::set_var"
|
||||
]
|
||||
|
|
Loading…
Reference in New Issue