Rust

Connect to FTP Through a SOCKS Proxy

Demonstrates connecting through a SOCKS proxy using SocksVersion, SocksHostname, SocksPort, SocksUsername, and SocksPassword.

Background: SOCKS is a general-purpose TCP relay, so it carries FTP transparently. SocksVersion is the switch — 0 disables it, while 4 or 5 selects the protocol. SOCKS5 supports username/password authentication and is the usual choice; SOCKS4 supports only a user identifier. Because FTP opens separate data connections, a SOCKS proxy combined with passive mode is generally the most reliable arrangement.

Chilkat Rust Downloads

Download Chilkat for Rust

Rust


let ftp = chilkat::Ftp2::new();

ftp.set_hostname("ftp.example.com");
ftp.set_username("myFtpLogin");

// SocksVersion selects the proxy: 0 (default) = none, 4 = SOCKS4, 5 = SOCKS5.
ftp.set_socks_version(5);
ftp.set_socks_hostname("socks.example.com");
ftp.set_socks_port(1080);

// SOCKS5 supports username/password authentication; SOCKS4 uses only a user identifier.
ftp.set_socks_username("myProxyLogin");
ftp.set_socks_password("myProxyPassword");

// Normally you would not hard-code the password in source.  You should instead obtain it
// from an interactive prompt, environment variable, or a secrets vault.
ftp.set_password("myPassword");

if ftp.connect().is_err() {
    println!("{}", ftp.last_error_text());
    return;
}

println!("Connected through the SOCKS proxy.");

if ftp.disconnect().is_err() {
    println!("{}", ftp.last_error_text());
    return;
}