RFC 4178: The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation Mechanism
In plain English — editorial summary, not part of the RFC
This document specifies a negotiation mechanism for the Generic Security Service Application Program Interface (GSS-API), which is described in RFC 2743. GSS-API peers can use this negotiation mechanism to choose from a common set of security mechanisms. If per-message integrity services are available on the established mechanism context, then the negotiation is protected against an attacker that forces the selection of a mechanism not desired by the peers. This mechanism replaces RFC 2478 in order to fix defects in that specification and to describe how to inter-operate with implementations of that specification that are commonly deployed on the Internet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4178
- Published
- October 2005
- Authors
- L. Zhu; P. Leach; K. Jaganathan; W. Ingersoll
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
- Obsoletes:
- RFC 2478
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1964The Kerberos Version 5 GSS-API MechanismUpdated
June 1996
- RFC 1961GSS-API Authentication Method for SOCKS Version 5Current
June 1996
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
- RFC 3542Advanced Sockets Application Program Interface (API) for IPv6Current
June 2003
- RFC 3493Basic Socket Interface Extensions for IPv6Current
March 2003
- RFC 2614An API for Service LocationCurrent
June 1999
- RFC 2553Basic Socket Interface Extensions for IPv6Obsoleted
March 1999
- RFC 2292Advanced Sockets API for IPv6Obsoleted
February 1998
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?