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: 2019-Feb-12
Document File: 2 page(s) / 3K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Leech: AUTHOR

Related Documents

10.17487/RFC1929: DOI

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". [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 61% 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 | +----+------+----------+------+----------+

Leech Standards Track [Page 1]

RFC 1929 Username Authentication for SOCKS V...

Processing...
Loading...