Permalink
Cannot retrieve contributors at this time
Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign up
Fetching contributors…
| use tokio_io::io::{read_exact, write_all, Window}; | |
| use futures::Future; | |
| use tokio_core::net::TcpStream; | |
| use tokio_core::reactor::Handle; | |
| use std::net::{SocketAddr, Ipv4Addr, Ipv6Addr, SocketAddrV4, SocketAddrV6}; | |
| use std::io::{self}; | |
| use futures::future; | |
| use utilities::{EitherFuture::{Left,Right},other,name_port,timeout}; | |
| use endpoint::{transfer,new_tcpendpoint}; | |
| // Data used to when processing a client to perform various operations over its | |
| // lifetime. | |
| pub struct Client { | |
| conn: Option<TcpStream>, | |
| //buffer: RcBuffer, | |
| //dns: BasicClientHandle, | |
| handle: Handle, | |
| addr: SocketAddr | |
| } | |
| impl Client { | |
| pub fn get_addr(&self) -> SocketAddr{ | |
| self.addr | |
| } | |
| pub fn new(s: TcpStream, h: &Handle, a: SocketAddr) -> Client { | |
| Client { conn:Some(s), handle: h.clone(), addr: a } | |
| } | |
| /// This is the main entry point for starting a SOCKS proxy connection. | |
| /// | |
| /// This function is responsible for constructing the future which | |
| /// represents the final result of the proxied connection. In this case | |
| /// we're going to return an `IoFuture<T>`, an alias for | |
| /// `Future<Item=T, Error=io::Error>`, which indicates how many bytes were | |
| /// proxied on each half of the connection. | |
| /// | |
| /// The first part of the SOCKS protocol with a remote connection is for the | |
| /// server to read one byte, indicating the version of the protocol. The | |
| /// `read_exact` combinator is used here to entirely fill the specified | |
| /// buffer, and we can use it to conveniently read off one byte here. | |
| /// | |
| /// Once we've got the version byte, we then delegate to the below | |
| /// `serve_vX` methods depending on which version we found. | |
| pub fn serve(mut self) | |
| -> impl Future<Item=(u64, u64), Error=io::Error> { | |
| let conn = self.conn.unwrap(); | |
| self.conn = None; | |
| read_exact(conn, [0u8]).and_then(move |(conn, buf)| { | |
| match buf[0] { | |
| v5::VERSION => Left(self.serve_v5(conn)), | |
| // If we hit an unknown version, we return a "terminal future" | |
| // which represents that this future has immediately failed. In | |
| // this case the type of the future is `io::Error`, so we use a | |
| // helper function, `other`, to create an error quickly. | |
| // | |
| // As version 4 was not supported, we change the word to "unsupported version". | |
| _ => Right(future::err(other("unsupported version"))), | |
| } | |
| }) | |
| } | |
| /// The meat of a SOCKSv5 handshake. | |
| /// | |
| /// This method will construct a future chain that will perform the entire | |
| /// suite of handshakes, and at the end if we've successfully gotten that | |
| /// far we'll initiate the proxying between the two sockets. | |
| /// | |
| /// As a side note, you'll notice a number of `.boxed()` annotations here to | |
| /// box up intermediate futures. From a library perspective, this is not | |
| /// necessary, but without them the compiler is pessimistically slow! | |
| /// Essentially, the `.boxed()` annotations here improve compile times, but | |
| /// are otherwise not necessary. | |
| fn serve_v5(self, conn: TcpStream) | |
| -> impl Future<Item=(u64, u64), Error=io::Error> { | |
| // First part of the SOCKSv5 protocol is to negotiate a number of | |
| // "methods". These methods can typically be used for various kinds of | |
| // proxy authentication and such, but for this server we only implement | |
| // the `METH_NO_AUTH` method, indicating that we only implement | |
| // connections that work with no authentication. | |
| // | |
| // First here we do the same thing as reading the version byte, we read | |
| // a byte indicating how many methods. Afterwards we then read all the | |
| // methods into a temporary buffer. | |
| // | |
| // Note that we use `and_then` here to chain computations after one | |
| // another, but it also serves to simply have fallible computations, | |
| // such as checking whether the list of methods contains `METH_NO_AUTH`. | |
| debug!("connected! SOCKS5"); | |
| let num_methods = read_exact(conn, [0u8]); | |
| let authenticated = num_methods.and_then(|(conn, buf)| { | |
| debug!("number of methods: {}", buf[0]); | |
| read_exact(conn, vec![0u8; buf[0] as usize]) | |
| }).and_then(|(conn, buf)| { | |
| if buf.contains(&v5::METH_NO_AUTH) { | |
| debug!("authenticated!"); | |
| Ok(conn) | |
| } else { | |
| Err(other("no supported method given")) | |
| } | |
| }); | |
| // After we've concluded that one of the client's supported methods is | |
| // `METH_NO_AUTH`, we "ack" this to the client by sending back that | |
| // information. Here we make use of the `write_all` combinator which | |
| // works very similarly to the `read_exact` combinator. | |
| let part1 = authenticated.and_then(|conn| { | |
| write_all(conn, [v5::VERSION, v5::METH_NO_AUTH]) | |
| }); | |
| // Next up, we get a selected protocol version back from the client, as | |
| // well as a command indicating what they'd like to do. We just verify | |
| // that the version is still v5, and then we only implement the | |
| // "connect" command so we ensure the proxy sends that. | |
| // | |
| // As above, we're using `and_then` not only for chaining "blocking | |
| // computations", but also to perform fallible computations. | |
| let ack = part1.and_then(|(conn, _)| confirm_v5(conn)); | |
| let addr = ack.and_then(parse_command); | |
| let handle = self.handle.clone(); | |
| let connected = addr.and_then(move |(c, addr)| connect_target(c, addr, handle)); | |
| let handshake_finish = connected.and_then(|(c1,c2,addr)| final_response(c1,c2,addr)); | |
| // Phew! If you've gotten this far, then we're now entirely done with | |
| // the entire SOCKSv5 handshake! | |
| // | |
| // In order to handle ill-behaved clients, however, we have an added | |
| // feature here where we'll time out any initial connect operations | |
| // which take too long. | |
| // | |
| let pair = timeout(&self.handle, handshake_finish, "timeout during handshake"); | |
| // At this point we've *actually* finished the handshake. Not only have | |
| // we read/written all the relevant bytes, but we've also managed to | |
| // complete in under our allotted timeout. | |
| // | |
| // At this point the remainder of the SOCKSv5 proxy is shuttle data back | |
| // and for between the two connections. That is, data is read from `c1` | |
| // and written to `c2`, and vice versa. | |
| // | |
| // To accomplish this, we put both sockets into their own `Rc` and then | |
| // create two independent `Transfer` futures representing each half of | |
| // the connection. These two futures are `join`ed together to represent | |
| // the proxy operation happening. | |
| let result = pair.and_then(|(c1, c2)| | |
| transfer(new_tcpendpoint(c1), new_tcpendpoint(c2))); | |
| //print_type_info("result", &result); | |
| result | |
| } | |
| } | |
| fn parse_command(conn:TcpStream) | |
| -> impl Future<Item=(TcpStream, SocketAddr), Error=io::Error> | |
| { | |
| let command = read_exact(conn, [0u8]).and_then(|(conn, buf)| { | |
| debug!("cmd {}", buf[0]); | |
| if buf[0] == v5::CMD_CONNECT { | |
| Ok(conn) | |
| } else { | |
| Err(other("unsupported command")) | |
| } | |
| }); | |
| let resv = command.and_then(|c| read_exact(c, [0u8]).map(|c| c.0)); | |
| let atyp = resv.and_then(|c| read_exact(c, [0u8])); | |
| atyp.and_then(move |(c, buf)| parse_addr(c, buf)) | |
| } | |
| fn confirm_v5(conn:TcpStream) | |
| -> impl Future<Item=TcpStream, Error=io::Error> | |
| { | |
| read_exact(conn, [0u8]).and_then(|(conn, buf)| { | |
| debug!("ack {}", buf[0]); | |
| if buf[0] == v5::VERSION { | |
| Ok(conn) | |
| } else { | |
| Err(other("didn't confirm with v5 version")) | |
| } | |
| }) | |
| } | |
| // After we've negotiated a command, there's one byte which is reserved | |
| // for future use, so we read it and discard it. The next part of the | |
| // protocol is to read off the address that we're going to proxy to. | |
| // This address can come in a number of forms, so we read off a byte | |
| // which indicates the address type (ATYP). | |
| // | |
| // Depending on the address type, we then delegate to different futures | |
| // to implement that particular address format. | |
| //let mut dns = self.dns.clone(); | |
| fn parse_addr(c:TcpStream, buf:[u8; 1]) | |
| -> impl Future<Item=(TcpStream, SocketAddr), Error=io::Error> | |
| { | |
| debug!("addr type: {}", buf[0]); | |
| match buf[0] { | |
| // For IPv4 addresses, we read the 4 bytes for the address as | |
| // well as 2 bytes for the port. | |
| v5::ATYP_IPV4 => { | |
| Left(Left(read_exact(c, [0u8; 6]).map(|(c, buf)| { | |
| let addr = Ipv4Addr::new(buf[0], buf[1], buf[2], buf[3]); | |
| let port = ((buf[4] as u16) << 8) | (buf[5] as u16); | |
| let addr = SocketAddrV4::new(addr, port); | |
| (c, SocketAddr::V4(addr)) | |
| }))) | |
| } | |
| // For IPv6 addresses there's 16 bytes of an address plus two | |
| // bytes for a port, so we read that off and then keep going. | |
| v5::ATYP_IPV6 => { | |
| Left(Right(read_exact(c, [0u8; 18]).map(|(conn, buf)| { | |
| let a = ((buf[0] as u16) << 8) | (buf[1] as u16); | |
| let b = ((buf[2] as u16) << 8) | (buf[3] as u16); | |
| let c = ((buf[4] as u16) << 8) | (buf[5] as u16); | |
| let d = ((buf[6] as u16) << 8) | (buf[7] as u16); | |
| let e = ((buf[8] as u16) << 8) | (buf[9] as u16); | |
| let f = ((buf[10] as u16) << 8) | (buf[11] as u16); | |
| let g = ((buf[12] as u16) << 8) | (buf[13] as u16); | |
| let h = ((buf[14] as u16) << 8) | (buf[15] as u16); | |
| let addr = Ipv6Addr::new(a, b, c, d, e, f, g, h); | |
| let port = ((buf[16] as u16) << 8) | (buf[17] as u16); | |
| let addr = SocketAddrV6::new(addr, port, 0, 0); | |
| (conn, SocketAddr::V6(addr)) | |
| }))) | |
| } | |
| // The SOCKSv5 protocol not only supports proxying to specific | |
| // IP addresses, but also arbitrary hostnames. This allows | |
| // clients to perform hostname lookups within the context of the | |
| // proxy server rather than the client itself. | |
| // | |
| // Since the first publication of this code, several | |
| // futures-based DNS libraries appeared, and as a demonstration | |
| // of integrating third-party asynchronous code into our chain, | |
| // we will use one of them, TRust-DNS. | |
| // | |
| // The protocol here is to have the next byte indicate how many | |
| // bytes the hostname contains, followed by the hostname and two | |
| // bytes for the port. To read this data, we execute two | |
| // respective `read_exact` operations to fill up a buffer for | |
| // the hostname. | |
| // | |
| // Finally, to perform the "interesting" part, we process the | |
| // buffer and pass the retrieved hostname to a query future if | |
| // it wasn't already recognized as an IP address. The query is | |
| // very basic: it asks for an IPv4 address with a timeout of | |
| // five seconds. We're using TRust-DNS at the protocol level, | |
| // so we don't have the functionality normally expected from a | |
| // stub resolver, such as sorting of answers according to RFC | |
| // 6724, more robust timeout handling, or resolving CNAME | |
| // lookups. | |
| v5::ATYP_DOMAIN => { | |
| debug!("domain!"); | |
| Right(Left(read_exact(c, [0u8]).and_then(|(conn, buf)| { | |
| read_exact(conn, vec![0u8; buf[0] as usize + 2]) | |
| }).and_then(move |(conn, buf)| { | |
| match name_port(&buf) { | |
| Ok(ad) => Left(future::ok((conn,ad))), | |
| Err(e) => Right(future::err(e)), | |
| } | |
| }))) | |
| } | |
| n => { | |
| let msg = format!("unknown ATYP received: {}", n); | |
| Right(Right(future::err(other(&msg)))) | |
| } | |
| } | |
| } | |
| // Now that we've got a socket address to connect to, let's actually | |
| // create a connection to that socket! | |
| // | |
| // To do this, we use our `handle` field, a handle to the event loop, to | |
| // issue a connection to the address we've figured out we're going to | |
| // connect to. Note that this `tcp_connect` method itself returns a | |
| // future resolving to a `TcpStream`, representing how long it takes to | |
| // initiate a TCP connection to the remote. | |
| // | |
| // We wait for the TCP connect to get fully resolved before progressing | |
| // to the next stage of the SOCKSv5 handshake, but we keep ahold of any | |
| // possible error in the connection phase to handle it in a moment. | |
| fn connect_target(c:TcpStream, addr:SocketAddr, handle: Handle) | |
| -> impl Future<Item=(TcpStream, Result<TcpStream,io::Error>, SocketAddr), Error=io::Error> | |
| { | |
| debug!("proxying to {}", addr); | |
| TcpStream::connect(&addr, &handle).then(move |c2| Ok((c, c2, addr))) | |
| } | |
| // Once we've gotten to this point, we're ready for the final part of | |
| // the SOCKSv5 handshake. We've got in our hands (c2) the client we're | |
| // going to proxy data to, so we write out relevant information to the | |
| // original client (c1) the "response packet" which is the final part of | |
| // this handshake. | |
| fn final_response(c1:TcpStream, c2:Result<TcpStream,io::Error>, addr:SocketAddr) | |
| -> impl Future<Item=(TcpStream, TcpStream), Error=io::Error> | |
| { | |
| let mut resp = [0u8; 32]; | |
| // VER - protocol version | |
| resp[0] = 5; | |
| // REP - "reply field" -- what happened with the actual connect. | |
| // | |
| // In theory this should reply back with a bunch more kinds of | |
| // errors if possible, but for now we just recognize a few concrete | |
| // errors. | |
| resp[1] = match c2 { | |
| Ok(..) => 0, | |
| Err(ref e) if e.kind() == io::ErrorKind::ConnectionRefused => 5, | |
| Err(..) => 1, | |
| }; | |
| // RSV - reserved | |
| resp[2] = 0; | |
| // ATYP, BND.ADDR, and BND.PORT | |
| // | |
| // These three fields, when used with a "connect" command | |
| // (determined above), indicate the address that our proxy | |
| // connection was bound to remotely. There's a variable length | |
| // encoding of what's actually written depending on whether we're | |
| // using an IPv4 or IPv6 address, but otherwise it's pretty | |
| // standard. | |
| let addr = match c2.as_ref().map(|r| r.local_addr()) { | |
| Ok(Ok(addr)) => addr, | |
| Ok(Err(..)) | | |
| Err(..) => addr, | |
| }; | |
| let pos = match addr { | |
| SocketAddr::V4(ref a) => { | |
| resp[3] = 1; | |
| resp[4..8].copy_from_slice(&a.ip().octets()[..]); | |
| 8 | |
| } | |
| SocketAddr::V6(ref a) => { | |
| resp[3] = 4; | |
| let mut pos = 4; | |
| for &segment in a.ip().segments().iter() { | |
| resp[pos] = (segment >> 8) as u8; | |
| resp[pos + 1] = segment as u8; | |
| pos += 2; | |
| } | |
| pos | |
| } | |
| }; | |
| resp[pos] = (addr.port() >> 8) as u8; | |
| resp[pos + 1] = addr.port() as u8; | |
| // Slice our 32-byte `resp` buffer to the actual size, as it's | |
| // variable depending on what address we just encoding. Once that's | |
| // done, write out the whole buffer to our client. | |
| // | |
| // The returned type of the future here will be `(TcpStream, | |
| // TcpStream)` representing the client half and the proxy half of | |
| // the connection. | |
| let mut w = Window::new(resp); | |
| w.set_end(pos + 2); | |
| write_all(c1, w).and_then(|(c1, _)| { | |
| c2.map(|c2| (c1, c2)) | |
| }) | |
| } | |
| // Various constants associated with the SOCKS protocol | |
| #[allow(dead_code)] | |
| mod v5 { | |
| pub const VERSION: u8 = 5; | |
| pub const METH_NO_AUTH: u8 = 0; | |
| pub const METH_GSSAPI: u8 = 1; | |
| pub const METH_USER_PASS: u8 = 2; | |
| pub const CMD_CONNECT: u8 = 1; | |
| pub const CMD_BIND: u8 = 2; | |
| pub const CMD_UDP_ASSOCIATE: u8 = 3; | |
| pub const ATYP_IPV4: u8 = 1; | |
| pub const ATYP_IPV6: u8 = 4; | |
| pub const ATYP_DOMAIN: u8 = 3; | |
| } |