Anonymity Support for Kerberos
RFC 8062
| Document | Type |
RFC - Proposed Standard
(February 2017; No errata)
Obsoletes RFC 6112
|
|
|---|---|---|---|
| Last updated | 2017-02-28 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Matt Rogers | ||
| Shepherd write-up | Show (last changed 2016-10-17) | ||
| IESG | IESG state | RFC 8062 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Stephen Farrell | ||
| Send notices to | mrogers@redhat.com | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) L. Zhu
Request for Comments: 8062 P. Leach
Obsoletes: 6112 Microsoft Corporation
Updates: 4120, 4121, 4556 S. Hartman
Category: Standards Track Hadron Industries
ISSN: 2070-1721 S. Emery, Ed.
Oracle
February 2017
Anonymity Support for Kerberos
Abstract
This document defines extensions to the Kerberos protocol to allow a
Kerberos client to securely communicate with a Kerberos application
service without revealing its identity, or without revealing more
than its Kerberos realm. It also defines extensions that allow a
Kerberos client to obtain anonymous credentials without revealing its
identity to the Kerberos Key Distribution Center (KDC). This
document updates RFCs 4120, 4121, and 4556. This document obsoletes
RFC 6112 and reclassifies that document as Historic. RFC 6112
contained errors, and the protocol described in that specification is
not interoperable with any known implementation. This specification
describes a protocol that interoperates with multiple
implementations.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8062.
Zhu, et al. Standards Track [Page 1]
RFC 8062 Kerberos Anonymity Support February 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Zhu, et al. Standards Track [Page 2]
RFC 8062 Kerberos Anonymity Support February 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Changes since RFC 6112 . . . . . . . . . . . . . . . . . 4
2. Conventions Used in This Document . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Protocol Description . . . . . . . . . . . . . . . . . . . . 6
4.1. Anonymity Support in AS Exchange . . . . . . . . . . . . 6
4.1.1. Anonymous PKINIT . . . . . . . . . . . . . . . . . . 7
4.2. Anonymity Support in TGS Exchange . . . . . . . . . . . . 8
4.3. Subsequent Exchanges and Protocol Actions Common to AS
and TGS for Anonymity Support . . . . . . . . . . . . . . 10
5. Interoperability Requirements . . . . . . . . . . . . . . . . 11
6. GSS-API Implementation Notes . . . . . . . . . . . . . . . . 11
7. PKINIT Client Contribution to the Ticket Session Key . . . . 12
7.1. Combining Two Protocol Keys . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
Show full document text