Re: [saag] Improving the CHAP protocol

Jim Schaad <ietf@augustcellars.com> Wed, 25 September 2019 17:35 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6844A120121 for <saag@ietfa.amsl.com>; Wed, 25 Sep 2019 10:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 X4AOeatftSoU for <saag@ietfa.amsl.com>; Wed, 25 Sep 2019 10:35:21 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A83B1201DE for <saag@ietf.org>; Wed, 25 Sep 2019 10:35:21 -0700 (PDT)
Received: from Jude (192.168.1.159) by mail2.augustcellars.com (192.168.1.201) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 25 Sep 2019 10:35:14 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: "'Black, David'" <David.Black@dell.com>, <saag@ietf.org>
References: <9641f69d-0ffb-1c1d-7fb6-98ef4a54ad2c@redhat.com> <1569087342890.52733@cs.auckland.ac.nz> <4354cf7e-74f2-d36c-5fa0-587a2118a507@redhat.com>, <CE03DB3D7B45C245BCA0D243277949363070E288@MX307CL04.corp.emc.com> <1569336830344.45369@cs.auckland.ac.nz> <CE03DB3D7B45C245BCA0D2432779493630711EBF@MX307CL04.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493630711EBF@MX307CL04.corp.emc.com>
Date: Wed, 25 Sep 2019 10:35:13 -0700
Message-ID: <01ae01d573c7$97de44b0$c79ace10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJuUtirWZsZ6Nr59C8ioM7oqEO5NwIncRnTAeAhwvEBcFmTvwHpYQBrAs21KHuluXE2MA==
Content-Language: en-us
X-Originating-IP: [192.168.1.159]
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/sPmutR_tQBNJFXsLZd6iBJcaUEo>
Subject: Re: [saag] Improving the CHAP protocol
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 17:35:24 -0000

If you do that, I don't know if you want SHA3-256 or SHAKE.  SHAKE seems to
be used more from what I have seen so far.

Jim


-----Original Message-----
From: saag <saag-bounces@ietf.org>; On Behalf Of Black, David
Sent: Wednesday, September 25, 2019 10:04 AM
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>;; saag@ietf.org
Subject: Re: [saag] Improving the CHAP protocol

Yes, and SHA3-256  while we're in there ... I plan to submit the request to
IANA to do that by early next week.

Thanks, --David

> -----Original Message-----
> From: Peter Gutmann <pgut001@cs.auckland.ac.nz>;
> Sent: Tuesday, September 24, 2019 10:54 AM
> To: Black, David; saag@ietf.org
> Cc: Maurizio Lombardi
> Subject: Re: [saag] Improving the CHAP protocol
> 
> 
> Black, David <David.Black@dell.com>; writes:
> 
> >The situation that we can't change is that iSCSI references the IANA 
> >PPP CHAP registry for CHAP hash algorithms.
> 
> So would the simplest solution then be just to add SHA-256 to the
registry?
> 
> Peter.

_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag