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.
tokio-rustls(4 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.1.15 | 0.3.31 | out of date |
| rustls ⚠️ | ^0.11 | 0.23.28 | out of date |
| tokio-io | ^0.1.3 | 0.1.13 | up to date |
| tokio-proto | ^0.1.1 | 0.1.1 | up to date |
(4 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| clap | ^2.26 | 4.5.40 | out of date |
| tokio-core | ^0.1.9 | 0.1.18 | up to date |
| tokio-file-unix | ^0.4 | 0.6.0 | out of date |
| webpki-roots | ^0.13 | 1.0.1 | out of date |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.