GSS-API Authentication Method for SOCKS Version 5
draft-ietf-aft-socks-gssapi-revisions-01
| Document | Type |
Expired Internet-Draft
(aft WG)
Expired & archived
|
|
|---|---|---|---|
| Author | David S. Miller | ||
| Last updated | 1999-06-25 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 provides the specification for the SOCKS V5 GSS-API authentication protocol, and in particular, the use of the Simple and Protected GSS API Negotiation (SPNEGO) mechanism. Use of the SPNEGO pseudo- mechanism is intended to maximize the chance of agreement of a security mechanism, and hence maximize interoperability. A message protection subnegotiation protocol is also specified, allowing peers to agree on which message protection services GSS-API encapsulated messages will be protected with: integrity, or integrity and confidentiality. Other GSS-API security services, normally optional with GSS-API, are specified for use with SOCKS 5.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)