Rust
Rust
SSH Through a SOCKS Proxy
See more SSH Examples
Demonstrates connecting to an SSH server through a SOCKS4 or SOCKS5 proxy. Set the SOCKS properties before calling Connect, and set SocksVersion to match the proxy server.
Background: SOCKS is a general-purpose TCP relay, so unlike an HTTP proxy it is designed from the start to carry arbitrary protocols — usually the smoother option for SSH. The version matters: SOCKS4 supports only a username with no password, while SOCKS5 supports full login/password authentication as well as IPv6 and remote DNS resolution. Note this is the inverse of dynamic port forwarding: here a SOCKS proxy is used to reach the SSH server, rather than SSH providing a SOCKS proxy.
Chilkat Rust Downloads
// This example requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
// Demonstrates connecting to an SSH server through a SOCKS4 or SOCKS5 proxy.
let ssh = chilkat::Ssh::new();
// Set the SOCKS proxy properties before connecting. The hostname may be a domain name or an
// IP address.
ssh.set_socks_hostname("socks.example.com");
ssh.set_socks_port(1080);
ssh.set_socks_username("mySocksLogin");
ssh.set_socks_password("mySocksPassword");
// Set the version to match the proxy server: 4 or 5.
// Note: SOCKS4 supports only a username, with no password. SOCKS5 supports full
// login/password authentication.
ssh.set_socks_version(5);
let hostname = "ssh.example.com".to_string();
let port = 22;
if ssh.connect(&hostname, port).is_err() {
println!("{}", ssh.last_error_text());
return;
}
println!("Connected to the SSH server through the SOCKS proxy.");
// 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.
let password = "mySshPassword".to_string();
if ssh.authenticate_pw("mySshLogin", &password).is_err() {
println!("{}", ssh.last_error_text());
return;
}
// ... use the SSH connection normally ...
ssh.disconnect();