Rust
Rust
FTP through SSH Tunnel with Dynamic Port Forwarding
See more FTP Examples
Demonstrates how to start a background thread that runs a portable SSH tunnel w/ dynamic port forwarding that the foreground thread can be used for establishing FTP sessions through an SSH tunnel.Note: Some developers may be accustomed to starting an stunnel.exe proxy from https://www.stunnel.org. The stunnel.exe is not necessary here. Chilkat's background thread fulfills the task of what the external stunnel.exe does. Therefore, your application is self-contained, meaning that it can run anywhere because the SSH tunnel proxy is built-in.
Chilkat Rust Downloads
// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
let _ = false;
let tunnel = chilkat::SshTunnel::new();
let ssh_hostname = "sftp.example.com".to_string();
let ssh_port = 22;
// Connect to an SSH server and establish the SSH tunnel:
if tunnel.connect(&ssh_hostname, ssh_port).is_err() {
println!("{}", tunnel.last_error_text());
return;
}
// Authenticate with the SSH server via a login/password
// or with a public key.
// This example demonstrates SSH password authentication.
if tunnel.authenticate_pw("mySshLogin", "mySshPassword").is_err() {
println!("{}", tunnel.last_error_text());
return;
}
// Indicate that the background SSH tunnel thread will behave as a SOCKS proxy server
// with dynamic port forwarding:
tunnel.set_dynamic_port_forwarding(true);
// We may optionally require that connecting clients authenticate with our SOCKS proxy server.
// To do this, set an inbound username/password. Any connecting clients would be required to
// use SOCKS5 with the correct username/password.
// If no inbound username/password is set, then our SOCKS proxy server will accept both
// SOCKS4 and SOCKS5 unauthenticated connections.
tunnel.set_inbound_socks_username("chilkat123");
tunnel.set_inbound_socks_password("password123");
// Start the listen/accept thread to begin accepting SOCKS proxy client connections.
// Listen on port 1080.
if tunnel.begin_accepting(1080).is_err() {
println!("{}", tunnel.last_error_text());
return;
}
// Now that a background thread is running a SOCKS proxy server that forwards connections
// through an SSH tunnel, it is possible to use any Chilkat implemented protocol that is SOCKS capable,
// such as HTTP, POP3, SMTP, IMAP, FTP, etc. The protocol may use SSL/TLS because the SSL/TLS
// will be passed through the SSH tunnel to the end-destination. Also, any number of simultaneous
// connections may be routed through the SSH tunnel.
let ftp = chilkat::Ftp2::new();
// Indicate that the HTTP object is to use our portable SOCKS proxy/SSH tunnel running in our background thread.
ftp.set_socks_hostname("localhost");
// The SocksPort must equal the port passed to BeginAccepting above.
ftp.set_socks_port(1080);
ftp.set_socks_version(5);
// The SOCKS5 login/password set here must equal the InboundSocksUsername/Password set above.
ftp.set_socks_username("chilkat123");
ftp.set_socks_password("password123");
// This is the actual FTP server domain or IP address, and the login/password for the user account on the destination FTP server.
ftp.set_hostname("ftp.someFtpServer.com");
ftp.set_username("myLogin");
ftp.set_password("myPassword");
ftp.set_auth_tls(true);
// Connect and login (via the SSH tunnel) to the FTP server.
if ftp.connect().is_err() {
println!("{}", ftp.last_error_text());
return;
}
// Change to the remote directory where the file is located.
// This step is only necessary if the file is not in the root directory
// for the FTP account.
if ftp.change_remote_dir("junk").is_err() {
println!("{}", ftp.last_error_text());
return;
}
let local_filename = "c:/temp/hamlet.xml".to_string();
let remote_filename = "hamlet.xml".to_string();
// Download a file. (the data connection is also automatically established through the
// SSH tunnel using dynamic port forwarding..)
if ftp.get_file(&remote_filename, &local_filename).is_err() {
println!("{}", ftp.last_error_text());
return;
}
// The disconnect is disconnecting with the FTP server and closes the SSH tunnel.
// The background tunnel thread is still running, and may be used for subsequent FTP connections,
// or even connections for any other purpose, such as HTTP, IMAP, SMTP, POP3, etc.
let _ = ftp.disconnect().is_ok();
// When the app is finished with the tunnel, it can cleanup..
// Stop the background listen/accept thread:
let wait_for_thread_exit = true;
if tunnel.stop_accepting(wait_for_thread_exit).is_err() {
println!("{}", tunnel.last_error_text());
return;
}
// Close the SSH tunnel (would also kick any remaining connected clients).
if tunnel.close_tunnel(wait_for_thread_exit).is_err() {
println!("{}", tunnel.last_error_text());
return;
}