Deps.rs

fie 0.16.3

[![dependency status](https://deps.rs/crate/fie/0.16.3/status.svg)](https://deps.rs/crate/fie/0.16.3)

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 fie

Dependencies

(15 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 data-encoding^22.6.0up to date
 dirs^35.0.1out of date
 futures-util^0.30.3.31up to date
 log^0.40.4.22up to date
 memmap^0.70.7.0up to date
 mime_guess^22.0.5up to date
 percent-encoding^2.12.3.1up to date
 rand^0.70.8.5out of date
 ring^0.160.17.8out of date
 serde^11.0.215up to date
 serde_derive^11.0.215up to date
 structopt^0.30.3.26up to date
 tokio ⚠️^0.21.41.1out of date
 toml^0.50.8.19out of date
 yukikaze^1.0.01.0.10up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.