Deps.rs

dekellum / blocking-permit

[![dependency status](https://deps.rs/repo/github/dekellum/blocking-permit/status.svg)](https://deps.rs/repo/github/dekellum/blocking-permit)

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 blocking-permit

Dependencies

(8 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes>=1.0.0, <1.21.6.0out of date
 futures-core>=0.3.1, <0.40.3.30up to date
 futures-channel>=0.3.1, <0.40.3.30up to date
 tao-log>=1.0.0, <1.11.0.1up to date
 num_cpus>=1.11.1, <1.141.16.0out of date
 futures-intrusive>=0.3.1, <0.50.5.0out of date
 tokio ⚠️>=1.0.1, <1.141.37.0out of date
 parking_lot>=0.10.0, <0.120.12.2out of date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 futures-executor>=0.3.1, <0.40.3.30up to date
 futures-util>=0.3.1, <0.40.3.30up to date
 lazy_static>=1.3.0, <1.51.4.0up to date
 rand>=0.8.0, <0.90.8.5up to date
 tempfile>=3.1.0, <3.33.10.1out of date
 piccolog>=1.0.0, <1.11.0.3up 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);