Features and Standards Compliance

Standards compliance

This page refers to where we think we're at in complying with all relevant standards documents. There may be bugs that prevent certain functionality from working, but this is what should work.

SOCKS4An older version of the socks protocol.Full support for this protocol.
SOCKS4aAn amendment to allow for server-side name resolution.Full support for this protocol.
SOCKS5 (RFC 1928)The current revision of the SOCKS protocol.Support for all core features except for GSSAPI - see below. So far, I have never seen a client that uses GSSAPI, so this is not a big issue in practice.
Username-password authentication (RFC 1929)A protocol to allow for simple clear text authentication.Full support for this protocol.
GSSAPI (RFC 1961)A high security protocol where all data between the SOCKS server and internal clients is encrypted.No support for this protocol.

Compliance with proposed standards

CHAPA high security protocol where authentication credentials are not sent in cleartext, but data is.Full support for this protocol.
HMAC-MD5The default and core method for the CHAP mechanism.Full support for this protocol.
SSLA high security protocol where TCP data between the SOCKS server and internal clients is encrypted.No support for this protocol.
CRAMA high security protocol where authentication credentials are not sent in cleartext, but data is.No support for this protocol; CRAM was quickly superseeded by CHAP.

Other features