Browse Prior Art Database

Username/Password Authentication for SOCKS V5 (RFC1929)

IP.com Disclosure Number: IPCOM000004166D
Original Publication Date: 1996-Mar-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 2 page(s) / 3K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Leech: AUTHOR

Abstract

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".

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 81% of the total text.

Network Working Group M. Leech

Request for Comments: 1929 Bell-Northern Research Ltd

Category: Standards Track March 1996

Username/Password Authentication for SOCKS V5

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

1. Introduction

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".

Note:

Unless otherwise noted, the decimal numbers appearing in packet-

format diagrams represent the length of the corresponding field, in

octets. Where a given octet must take on a specific value, the

syntax X'hh' is used to denote the value of the single octet in that

field. When the word 'Variable' is used, it indicates that the

corresponding field has a variable length defined either by an

associated (one or two octet) length field, or by a data type field.

2. Initial negotiation

Once the SOCKS V5 server has started, and the client has selected the

Username/Password Authentication protocol, the Username/Password

subnegotiation begins. This begins with the client producing a

Username/Password request:

+----+------+----------+------+----------+

|VER | ULEN | UNAME | PLEN | PASSWD |

+----+------+----------+------+----------+

| 1 | 1 | 1 to 255 | 1 | 1 to 255 |

+----+------+----------+------+----------+

The VER field contains the current version of the subnegotiation,

which is X'01'. The ULEN field contains the length of the UNAME field

that follows. The UNAME field contains the username as known to the

source operating system. The PLEN field contains the length of the

PASSWD field that follows. The PASSWD field contains the password

association with the given UNAME.

The server verifies the supplied UNAME and PASSWD, and sends the

following response:

+----+--------+

|VER | STATUS |

+----+--------+

| 1 | 1 |

+----+--------+

A STA...