Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review
Loganaden Velvindron <logan@hackers.mu> Thu, 09 August 2018 11:06 UTC
Return-Path: <logan@hackers.mu>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA1D130E1C for <curdle@ietfa.amsl.com>; Thu, 9 Aug 2018 04:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hackers-mu.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRIRNIEEgV_R for <curdle@ietfa.amsl.com>; Thu, 9 Aug 2018 04:06:32 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3D7A130E17 for <curdle@ietf.org>; Thu, 9 Aug 2018 04:06:32 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id j205-v6so9116746oib.4 for <curdle@ietf.org>; Thu, 09 Aug 2018 04:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hackers-mu.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iq5XMIH2OukQZnOGm9pv8++1AtyAJgRPd6yVXjubV5Q=; b=dhwrB+5eSEoPPFl5pL1LavcMLii8qjog7bQ4Xn0T7QpV3qcdB0beX23MnlgR1XnvPK peNUXG1JWLkevKuCm6Dsb2Q16wQcyjliG/K7PZqrOAYoZ9jSXIrVfVwBoUh42eWtMRdq 2cZXq8lxB7ek/UTb7qHCF7eP2qwUeCHXFp+mjR6bCLKLAperSCXQX4QE8qY7wh8wlOlh atZ6Z4CzhEDaKnq2RfdSQeOatDNdSqbKA4F6CnjOywciAFin5FICeiYbVuCiCsSH5xbV ZuNk72qY3zi2O6yb9EKLrtld2mS6cRWDuIfc3yjfJQicCgK8/em99uAKt+k5o0IZXJGB wx4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iq5XMIH2OukQZnOGm9pv8++1AtyAJgRPd6yVXjubV5Q=; b=pjl1BD8UGwndbxuJsqGYXxbgUYdF7BZRBiyL6BMfBI+IJ5Q+jDgGMDNDnWxhIPhbi/ RFCjukFrj2UkvCZ/pDc0TERam0Pn+gtENbom3P1d6T4gd5xcJXJR9rWuj7ArjFChp5QT 8l9bvCSoGiEEQwIUgByeuTqZaR8AO+K2ocTtDshuZL39rtPTKf0dJvphntMiXutmAXHB h0ktcu5HmRuWvkEvs0BPL9FTR5r9uPJx0LjtUF/iuYGXRVIphrSwUVW37Y6krEG7KPvh LLplwDmAG6VnbaRl1oYkKNP4D0nKbwGMaJAQCPGbp2QR35u08rDWkgh3QEqIpGfQji+m NlQA==
X-Gm-Message-State: AOUpUlHlr4zKptEs2b11k9xvphLjE5kmsSbV5gkLhPREv8aXW6YQFBka vworVsy9Eo+dT89PvjbjKyqAoofOfyEAywaVeqo/Kw==
X-Google-Smtp-Source: AA+uWPw7LZ18z2QtilyO4ijaOv2Qa12aAqL6QjKADDp7QlfQ460HVN0yEABrMCI7Bj4YbPYtnFP3043ePL7AZsjbwP8=
X-Received: by 2002:aca:abc6:: with SMTP id u189-v6mr1703407oie.61.1533812791892; Thu, 09 Aug 2018 04:06:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:ad8f:0:0:0:0:0 with HTTP; Thu, 9 Aug 2018 04:06:30 -0700 (PDT)
In-Reply-To: <CADZyTk=_MU7rB2JiXqcc+nzx4SocEZCXa7NUcd+gwYVKmQANKA@mail.gmail.com>
References: <CADZyTkkv=m7N2ztwfqz2M4C=maai1-Djyfwrf4TzL3Pt=-ujdg@mail.gmail.com> <CADZyTkn-AtKgn4Z28NUfu1fOjN6XV43m1uNWf_ge3T6_0o0pbQ@mail.gmail.com> <CADZyTk=_MU7rB2JiXqcc+nzx4SocEZCXa7NUcd+gwYVKmQANKA@mail.gmail.com>
From: Loganaden Velvindron <logan@hackers.mu>
Date: Thu, 09 Aug 2018 15:06:30 +0400
Message-ID: <CAFDEUTcmQqZ-3SubDNJVDZjzovNLXq1Q+G5FyVrV5VON0V4Wqw@mail.gmail.com>
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: curdle <curdle@ietf.org>
Content-Type: multipart/mixed; boundary="0000000000009d18440572fe9e3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/B24g7D0rbjDjAHmxWmPvoNAn3Ng>
Subject: Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2018 11:06:36 -0000
Please find attached the revised xml file for rev 07, with the feedback received. I'm going to upload once the chairs clear this: https://datatracker.ietf.org/submit/status/97172/ On Tue, Jul 17, 2018 at 9:58 PM, Daniel Migault <daniel.migault@ericsson.com> wrote: > Hi, > > We would like to thank Loganaden Velvindron for volunteering to co-author > and move the draft forward. > > Yours, > Daniel > > On Fri, Jul 6, 2018 at 5:13 PM, Daniel Migault <daniel.migault@ericsson.com> > wrote: >> >> Hi, >> >> We would like to move the draft to the IESG, however, the draft has not >> been updated to address the comments received on the mailing list. We have >> privately contacted the author 3 times with the email address provided to >> the draft, but we did not receive any response. The purpose of this email is >> to first try to contact the author of draft via another channel and >> understand if he has any plan to move the draft forward. In addition, we >> would also like to see if there is any interest by some members of the group >> to co-author the draft and move the draft forward. For those interested in >> co-authoring the draft, please contact us privately. >> >> Our goal is to have all drafts - that is the two remaining drafts in WGLC >> - submitted by end of august. >> >> Yours, >> Rich and Daniel >> >> On Tue, May 15, 2018 at 1:00 PM, Daniel Migault >> <daniel.migault@ericsson.com> wrote: >>> >>> Hi, >>> >>> Please find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I >>> have also proposed text, so please comment the review in the mail. I am >>> willing to start a WGLC as soon as the draft is being updated. >>> >>> Yours, >>> Daniel >>> >>> >>> [1] https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-06 >>> >>> >>> RFC-Editor: >>> >>> I personally find the ton of the sentence a bit aggressive, thus I would >>> remove it or just leave the RFC reference. >>> >>> """ >>> Non-ASCII characters are allowed in RFCs as per RFC 7997. >>> """ >>> >>> I see deprecation and move to historic status as very similar to >>> draft-ietf-curdle-des-des-des-die-die-die-05 and I assume that is correct. >>> >>> Abstract: >>> >>> The sentence below is a bit hard to parse. >>> "" >>> and formally obsoletes and moves to >>> Historic RFC 4345. >>> "" >>> >>> I would propose instead: >>> >>> """ >>> This document deprecates RC4 in Secure Shell (SSH). Therefore, this >>> document updates RFC 4253, and moves to Historic RFC 4345. >>> """ >>> >>> 1. Introduction >>> >>> >>> """ >>> RC4 is broken"" >>> """ >>> >>> Although English is not my main language, it sounds a bit abrupt to me >>> and it might be preferred to sue something around the lines of >>> draft-ietf-curdle-des-des-des-die-die-die-05: >>> >>> RC4 encryption is steadily weakening in cryptographic strength, and the >>> deprecation process should be begun for their use in SSH. >>> >>> >>> It seems to me that sections 1, 2 3 could be merged. I would propose the >>> following text. I am providing comments in <mglt></mglt>. >>> >>> >>> >>> 1. Introduction >>> >>> >>> The usage of RC4 suites ( also designated as arcfour ) for SSH are >>> specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation of the >>> "arcfour" cipher for SSH. RFC 4345 specifies and allocates the the >>> "arcfour-128" and "arcfour-256" ciphers for SSH. >>> >>> RC4 encryption is steadily weakening in cryptographic strength >>> [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the deprecation >>> process should be begun for their use in Secure Shell (SSH) [RFC4253]. >>> Accordingly, RFC 4253 is updated to note the deprecation of the RC4 ciphers >>> and RFC 4345 is moved to Historic as all ciphers it specifies MUST NOT be >>> used. >>> >>> <mglt>I believe that this document is very closed to >>> [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a reference to it >>> should be mentioned. </mglt> >>> >>> >>> 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 BCP 14 [RFC2119, RFC8174] >>> when, and only when, they appear in all capitals, as shown here. >>> >>> 3. Updates to RFC 4253 >>> >>> RFC 4253 is updated to prohibit arcfour's use in SSH. >>> >>> <mglt> >>> """ >>> The last sentence of the paragraph on RC4 (called "arcfour" >>> in [RFC4253]) in Section 6.3 of [RFC4253] >>> """ >>> >>> I believe that it might be clearer to quote the text as it is not easy to >>> locate it. I would propose the text below. </mglt> >>> >>> RFC 4253 allocate the "arcfour" cipher in Section 6.3 by defining a list >>> of defined ciphers where the "arcfour" cipher appears as optional as >>> mentioned below: >>> >>> """ >>> arcfour OPTIONAL the ARCFOUR stream cipher >>> with a 128-bit key >>> """ >>> >>> The current document updates the status of the "arcfour" ciphers in the >>> list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUST NOT. >>> >>> """ >>> arcfour MUST NOT the ARCFOUR stream cipher >>> with a 128-bit key >>> """ >>> >>> RFC 4253 defines the "arcfour" ciphers with the text mentioned below: >>> """ >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >>> The Arcfour cipher is believed to be compatible with the RC4 cipher >>> [SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and >>> should be used with caution. >>> """ >>> >>> The current document updates RFC 4253 Section 6.3 by replacing th etext >>> above with the following text: >>> >>> """ >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >>> The Arcfour cipher is believed to be compatible with the RC4 cipher >>> [SCHNEIER]. Arcfour (and RC4) is steadily weakening in cryptographic >>> strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and >>> MUST NOT be used. >>> """ >>> >>> 4. IANA Considerations >>> >>> <mglt>There is a reference to 3DES i think should be removed. In >>> addition, IANA cannot be required to update RFCs. IANA is assigned to update >>> the SSH registries. With [IANA] being an informational reference to >>> https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml, I >>> would propose the following text :</mglt> >>> >>> The IANA is requested to update the Encryption Algorithm Name Registry >>> of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration >>> procedure is IETF Review which is achieved by this document. The registry >>> should be updated as follows: >>> >>> Encryption Algorithm Name Reference Note >>> arcfour [RFC-TBD] >>> arcfour128 [RFC-TBD] >>> arcfour256 [RFC-TBD] >>> >>> >>> Where TBD is the RFC number assigned to the document. >>> >>> >>> >> > > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle >
- Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06… Daniel Migault
- [Curdle] draft-ietf-curdle-rc4-die-die-die-06 rev… Daniel Migault
- Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06… Daniel Migault
- Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06… Loganaden Velvindron
- Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06… Daniel Migault