Deprecate 3DES and RC4 in Kerberos
draft-ietf-curdle-des-des-des-die-die-die-05

Document Type Active Internet-Draft (curdle WG)
Last updated 2017-09-18
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Daniel Migault
Shepherd write-up Show (last changed 2017-07-11)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Eric Rescorla
Send notices to Daniel Migault <daniel.migault@ericsson.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                           B. Kaduk
Internet-Draft                                                    Akamai
Updates: 3961,4120 (if approved)                                M. Short
Intended status: Best Current Practice             Microsoft Corporation
Expires: March 22, 2018                               September 18, 2017

                   Deprecate 3DES and RC4 in Kerberos
              draft-ietf-curdle-des-des-des-die-die-die-05

Abstract

   The 3DES and RC4 encryption types are steadily weakening in
   cryptographic strength, and the deprecation process should be begun
   for their use in Kerberos.  Accordingly, RFC 4757 is moved to
   Historic status, as none of the encryption types it specifies should
   be used, and RFC 3961 is updated to note the deprecation of the
   triple-DES encryption types.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 22, 2018.

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
   (https://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

Kaduk & Short            Expires March 22, 2018                 [Page 1]
Internet-Draft     Deprecate 3DES and RC4 in Kerberos     September 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   3.  Affected Specifications . . . . . . . . . . . . . . . . . . .   2
   4.  Affected Encryption Types . . . . . . . . . . . . . . . . . .   3
   5.  RC4 Weakness  . . . . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Statistical Biases  . . . . . . . . . . . . . . . . . . .   3
     5.2.  Password Hash . . . . . . . . . . . . . . . . . . . . . .   4
     5.3.  Cross-Protocol Key Reuse  . . . . . . . . . . . . . . . .   5
     5.4.  Interoperability Concerns . . . . . . . . . . . . . . . .   5
   6.  3DES Weakness . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Password-based Keys . . . . . . . . . . . . . . . . . . .   6
     6.2.  Block Size  . . . . . . . . . . . . . . . . . . . . . . .   6
     6.3.  Interoperability  . . . . . . . . . . . . . . . . . . . .   6
   7.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The 3DES and RC4 encryption types are steadily weakening in
   cryptographic strength, and the deprecation process should be begun
   for their use in Kerberos.  Accordingly, RFC 4757 is moved to
   Historic status, as none of the encryption types it specifies should
   be used, and RFC 3961 is updated to note the deprecation of the
   triple-DES encryption types.

2.  Requirements Notation

   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 [RFC2119].

3.  Affected Specifications

   The RC4 Kerberos encryption types are specified in [RFC4757], which
Show full document text