4402
HISTORIC
A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) Mechanism (Obsoleted)
Authors: N. Williams
Date: February 2006
Area: sec
Working Group: kitten
Stream: IETF
Obsoleted by:
RFC 7802
Abstract
This document defines the Pseudo-Random Function (PRF) for the Kerberos V mechanism for the Generic Security Service Application Program Interface (GSS-API), based on the PRF defined for the Kerberos V cryptographic framework, for keying application protocols given an established Kerberos V GSS-API security context. [STANDARDS-TRACK]
RFC 4402
Obsoleted by: 7802 HISTORIC
Errata Exist
Network Working Group N. Williams
Request for Comments: 4402 Sun
Category: Standards Track February 2006
<span class="h1">A Pseudo-Random Function (PRF) for the Kerberos V Generic Security</span>
<span class="h1">Service Application Program Interface (GSS-API) Mechanism</span>
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.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document defines the Pseudo-Random Function (PRF) for the
Kerberos V mechanism for the Generic Security Service Application
Program Interface (GSS-API), based on the PRF defined for the
Kerberos V cryptographic framework, for keying application protocols
given an established Kerberos V GSS-API security context.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Kerberos V GSS Mechanism PRF ....................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Normative References ............................................<a href="#page-4">4</a>
<span class="grey">Williams Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc4402">RFC 4402</a> A PRF for the Kerberos V Mechanism February 2006</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies the Kerberos V GSS-API mechanism's [<a href="./rfc4121" title=""The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2"">RFC4121</a>]
pseudo-random function corresponding to [<a href="./rfc4401" title=""A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)"">RFC4401</a>]. The function is a
"PRF+" style construction. For more information see [<a href="./rfc4401" title=""A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)"">RFC4401</a>],
[<a href="./rfc2743" title=""Generic Security Service Application Program Interface Version 2, Update 1"">RFC2743</a>], [<a href="./rfc2744" title=""Generic Security Service API Version 2 : C-bindings"">RFC2744</a>], and [<a href="./rfc4121" title=""The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2"">RFC4121</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Kerberos V GSS Mechanism PRF</span>
The GSS-API PRF [<a href="./rfc4401" title=""A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)"">RFC4401</a>] function for the Kerberos V mechanism
[<a href="./rfc4121" title=""The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2"">RFC4121</a>] shall be the output of a PRF+ function based on the
encryption type's PRF function keyed with the negotiated session key
of the security context corresponding to the 'prf_key' input
parameter of GSS_Pseudo_random().
This PRF+ MUST be keyed with the key indicated by the 'prf_key' input
parameter as follows:
o GSS_C_PRF_KEY_FULL -- use the sub-session key asserted by the
acceptor, if any, or the sub-session asserted by the initiator, if
any, or the Ticket's session key
o GSS_C_PRF_KEY_PARTIAL -- use the sub-session key asserted by the
initiator, if any, or the Ticket's session key
The PRF+ function is a simple counter-based extension of the Kerberos
V pseudo-random function [<a href="./rfc3961" title=""Encryption and Checksum Specifications for Kerberos 5"">RFC3961</a>] for the encryption type of the
security context's keys:
PRF+(K, L, S) = truncate(L, T1 || T2 || .. || Tn)
Tn = pseudo-random(K, n || S)
where '||' is the concatenation operator, 'n' is encoded as a network
byte order 32-bit unsigned binary number, truncate(L, S) truncates
the input octet string S to length L, and pseudo-random() is the
Kerberos V pseudo-random function [<a href="./rfc3961" title=""Encryption and Checksum Specifications for Kerberos 5"">RFC3961</a>].
The maximum output size of the Kerberos V mechanism's GSS-API PRF
then is, necessarily, 2^32 times the output size of the pseudo-
random() function for the encryption type of the given key.
<span class="grey">Williams Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc4402">RFC 4402</a> A PRF for the Kerberos V Mechanism February 2006</span>
When the input size is longer than 2^14 octets as per [<a href="./rfc4401" title=""A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)"">RFC4401</a>] and
exceeds an implementation's resources, then the mechanism MUST return
GSS_S_FAILURE and GSS_KRB5_S_KG_INPUT_TOO_LONG as the minor status
code.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
This document has no IANA considerations currently. If and when a
relevant IANA registry of GSS-API symbols and constants is created,
then the GSS_KRB5_S_KG_INPUT_TOO_LONG minor status code should be
added to such a registry.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Kerberos V encryption types' PRF functions use a key derived from
contexts' session keys and should preserve the forward security
properties of the mechanisms' key exchanges.
Legacy Kerberos V encryption types may be weak, particularly the
single-DES encryption types.
See also [<a href="./rfc4401" title=""A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)"">RFC4401</a>] for generic security considerations of
GSS_Pseudo_random().
See also [<a href="./rfc3961" title=""Encryption and Checksum Specifications for Kerberos 5"">RFC3961</a>] for generic security considerations of the
Kerberos V cryptographic framework.
Use of Ticket session keys, rather than sub-session keys, when
initiators and acceptors fail to assert sub-session keys, is
dangerous as ticket reuse can lead to key reuse; therefore,
initiators should assert sub-session keys always, and acceptors
should assert sub-session keys at least when initiators fail to do
so.
The computational cost of computing this PRF+ may vary depending on
the Kerberos V encryption types being used, but generally the
computation of this PRF+ gets more expensive as the input and output
octet string lengths grow (note that the use of a counter in the PRF+
construction allows for parallelization). This means that if an
application can be tricked into providing very large input octet
strings and requesting very long output octet strings, then that may
constitute a denial of service attack on the application; therefore,
applications SHOULD place appropriate limits on the size of any input
octet strings received from their peers without integrity protection.
<span class="grey">Williams Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc4402">RFC 4402</a> A PRF for the Kerberos V Mechanism February 2006</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2743">RFC2743</a>] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", <a href="./rfc2743">RFC 2743</a>, January 2000.
[<a id="ref-RFC2744">RFC2744</a>] Wray, J., "Generic Security Service API Version 2 :
C-bindings", <a href="./rfc2744">RFC 2744</a>, January 2000.
[<a id="ref-RFC3961">RFC3961</a>] Raeburn, K., "Encryption and Checksum Specifications for
Kerberos 5", <a href="./rfc3961">RFC 3961</a>, February 2005.
[<a id="ref-RFC4121">RFC4121</a>] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos
Version 5 Generic Security Service Application Program
Interface (GSS-API) Mechanism: Version 2", <a href="./rfc4121">RFC 4121</a>,
July 2005.
[<a id="ref-RFC4401">RFC4401</a>] Williams, N., "A Pseudo-Random Function (PRF) API
Extension for the Generic Security Service Application
Program Interface (GSS-API)", <a href="./rfc4401">RFC 4401</a>, February 2006.
Author's Address
Nicolas Williams
Sun Microsystems
5300 Riata Trace Ct
Austin, TX 78727
US
EMail: [email protected]
<span class="grey">Williams Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc4402">RFC 4402</a> A PRF for the Kerberos V Mechanism February 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
[email protected].
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Williams Standards Track [Page 5]
Annotations
Select text to annotate