RFC 1929: Username/Password Authentication for SOCKS V5
In plain English — editorial summary, not part of the RFC
The protocol specification for SOCKS Version 5 specifies a generalized framework for the use of arbitrary authentication protocols in the initial socks connection setup. This document describes one of those protocols, as it fits into the SOCKS Version 5 authentication "subnegotiation". [STANDARDS-TRACK]
Document record
- Document ID
- RFC1929
- Published
- March 1996
- Authors
- M. Leech
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 2
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1928SOCKS Protocol Version 5Current
March 1996
- RFC 1938A One-Time Password SystemObsoleted
May 1996
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 2065Domain Name System Security ExtensionsObsoleted
January 1997
- RFC 2078Generic Security Service Application Program Interface, Version 2Obsoleted
January 1997
- RFC 2084Considerations for Web Transaction SecurityCurrent
January 1997
- RFC 2228FTP Security ExtensionsCurrent
October 1997
- RFC 2246The TLS Protocol Version 1.0Obsoleted
January 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?