Deps.rs

iotaledger / stronghold.rs

[![dependency status](https://deps.rs/repo/github/iotaledger/stronghold.rs/status.svg)](https://deps.rs/repo/github/iotaledger/stronghold.rs)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate stronghold_engine

Dependencies

(10 total, 1 outdated)

CrateRequiredLatestStatus
 thiserror^1.01.0.59up to date
 anyhow^1.01.0.82up to date
 dirs-next^2.02.0.0up to date
 hex^0.4.20.4.3up to date
 paste^1.0.11.0.14up to date
 once_cell^1.41.19.0up to date
 zeroize^1.5.71.7.0up to date
 serde^1.01.0.198up to date
 digest^0.10.10.10.7up to date
 iota-crypto^0.18.00.23.1out of date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 tempfile^3.1.03.10.1up to date
 proptest^1.0.01.4.0up to date
 criterion^0.40.5.1out of date
 json^0.120.12.4up to date

Crate stronghold-runtime

Dependencies

(9 total, 2 outdated)

CrateRequiredLatestStatus
 libc^0.20.2.153up to date
 log^0.4.170.4.21up to date
 zeroize^1.5.71.7.0up to date
 libsodium-sys^0.20.2.7up to date
 serde^1.01.0.198up to date
 rand^0.8.40.8.5up to date
 dirs^4.0.05.0.1out of date
 thiserror^1.01.0.59up to date
 iota-crypto^0.18.00.23.1out of date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 serde_json^1.01.0.116up to date
 env_logger^0.90.11.3out of date
 dhat^0.30.3.3up to date
 criterion^0.40.5.1out of date

Crate stronghold_native

Dependencies

(8 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 libc^0.2.20.2.153up to date
 thiserror^1.0.301.0.59up to date
 tokio ⚠️^1.15.01.37.0maybe insecure
 base64^0.13.00.22.0out of date
 iota-crypto^0.18.00.23.1out of date
 lazy_static^1.4.01.4.0up to date
 env_logger^0.9.00.11.3out of date
 log^0.4.140.4.21up to date

Crate iota_stronghold

Dependencies

(9 total, 2 outdated)

CrateRequiredLatestStatus
 thiserror^1.0.301.0.59up to date
 zeroize^1.5.71.7.0up to date
 serde^1.01.0.198up to date
 iota-crypto^0.18.00.23.1out of date
 hkdf^0.120.12.4up to date
 bincode^1.31.3.3up to date
 pin-project^1.0.101.1.5up to date
 futures^0.3.210.3.30up to date
 rust-argon2=1.0.02.1.0out of date

Dev dependencies

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.15.01.37.0maybe insecure
 criterion^0.40.5.1out of date
 env_logger^0.9.00.11.3out of date
 ctor^0.1.210.2.8out of date
 rand^0.8.40.8.5up to date
 clap^3.1.64.5.4out of date
 log^0.4.140.4.21up to date
 base64^0.13.00.22.0out of date
 regex^1.5.51.10.4up to date
 libc^0.20.2.153up to date
 threadpool^1.81.8.1up to date

Crate stronghold-utils

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 rand^0.8.30.8.5up to date

Crate stronghold-derive

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 syn^1.02.0.60out of date
 quote^1.01.0.36up to date
 proc-macro2^1.01.0.81up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);