As per Relevance of the word contains, we have this rfc below:
Network Working Group M.
Request for Comments: 1929 Bell-Northern Research
Category: Standards Track March 1996
Username/Password Authentication for SOCKS V
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
1.
The protocol specification for SOCKS Version 5 specifies
generalized framework for the use of arbitrary
protocols in the initial socks connection setup. This
describes one of those protocols, as it fits into the SOCKS Version 5
authentication "subnegotiation".
Note
Unless otherwise noted, the decimal numbers appearing in packet
format diagrams represent the length of the corresponding field,
octets. Where a given octet must take on a specific value,
syntax X'hh' is used to denote the value of the single octet in
field. When the word 'Variable' is used, it indicates that
corresponding field has a variable length defined either by
associated (one or two octet) length field, or by a data type field
2. Initial
Once the SOCKS V5 server has started, and the client has selected
Username/Password Authentication protocol, the Username/
subnegotiation begins. This begins with the client producing
Username/Password request
+----+------+----------+------+----------+
|VER | ULEN | UNAME | PLEN | PASSWD |
+----+------+----------+------+----------+
| 1 | 1 | 1 to 255 | 1 | 1 to 255 |
+----+------+----------+------+----------+
Leech Standards Track [Page 1]
RFC 1929 Username Authentication for SOCKS V5 March 1996
The VER field contains the current version of the subnegotiation
which is X'01'. The ULEN field contains the length of the UNAME
that follows. The UNAME field contains the username as known to
source operating system. The PLEN field contains the length of
PASSWD field that follows. The PASSWD field contains the
association with the given UNAME
The server verifies the supplied UNAME and PASSWD, and sends
following response
+----+--------+
|VER | STATUS |
+----+--------+
| 1 | 1 |
+----+--------+
A STATUS field of X'00' indicates success. If the server returns
`failure' (STATUS value other than X'00') status, it MUST close
connection
3. Security
This document describes a subnegotiation that provides
services to the SOCKS protocol. Since the request carries
password in cleartext, this subnegotiation is not recommended
environments where "sniffing" is possible and practical
4. Author's
Marcus
Bell-Northern Research
P.O. Box 3511, Station
Ottawa,
CANADA K1Y 4H
Phone: +1 613 763 9145
EMail: mleech@bnr.
Leech Standards Track [Page 2]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
