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 t-rec

Dependencies

(19 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tempfile^3.233.27.0up to date
 rayon^1.111.12.0up to date
 log^0.40.4.30up to date
 env_logger^0.110.11.10up to date
 humantime^2.32.3.0up to date
 simplerand^1.61.6.0up to date
 serde^1.01.0.228up to date
 toml^1.01.1.2+spec-1.1.0up to date
 dirs^6.06.0.0up to date
 dialoguer^0.120.12.0up to date
 crossterm^0.290.29.0up to date
 tokio ⚠️^11.52.3maybe insecure
 clap^4.54.6.1up to date
 image^0.250.25.10up to date
 nix^0.310.31.3up to date
 libc^0.20.2.186up to date
 x11rb^0.130.13.2up to date
 win-screenshot^4.04.0.14up to date
 windows^0.610.62.2out of 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);