rust_async_ftp

rust_async_ftp copied to clipboard

This PR fixes vulnerability [CVE-2020-26235](https://nvd.nist.gov/vuln/detail/CVE-2020-26235). It removes default features for chrono in order to eliminate subdependency on [email protected]. Removing this subdependency is required by an advisory https://github.com/chronotope/chrono/issues/602.

mihaigalos

Rather than using the IP provided by the server in the response to PASV, use the IP of the server we are connected to. This is more secure since we...

oscarwcl

This commit: - updates tokio & tokio-rustls dependencies - eliminates a compiler warning - changes the integration test to look for the ftp server at ":::21"

sp1ff

Not an issue as such, but I couldn't find any contact information on your Github profile-- is this crate/repo still being maintained?

sp1ff

Example: ```rust use async_ftp::FtpStream; use std::convert::TryFrom; use tokio_rustls::rustls::{ClientConfig, RootCertStore, ServerName}; #[tokio::main] async fn main() { let ftp_stream = FtpStream::connect("lettir.orangewebsite.com:21") .await .unwrap(); let mut root_store = RootCertStore::empty(); // root_store.add_pem_file(...); let conf...

sp1ff

Signed-off-by: Jiahao XU

NobodyXu

NobodyXu

Once the client has finished reading a file from the server, the server sends a status message to the client. The current API of FtpStream::get doesn't allow us to read...

oscarwcl

The documentation in the crate root explains that you need to enable the `openssl` feature to enable support for FTPS, but `Cargo.toml` only features a dependency on tokio-rustls.

djc

While `FtpStream::retr()` tries to read a status after reading from the stream, it looks like `FtpStream::get()` doesn't do this. When we wrote some code that calls `get()` and completes successfully,...

djc