IETF Logo Mail Archive

Re: [saag] RADIUS is deprecating MD5

Viktor Dukhovni <ietf-dane@dukhovni.org> Sun, 31 March 2024 16:29 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 4E67BC14F5FC for <saag@ietfa.amsl.com>; Sun, 31 Mar 2024 09:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dukhovni.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdRsilwOReiW for <saag@ietfa.amsl.com>; Sun, 31 Mar 2024 09:29:29 -0700 (PDT)
Received: from chardros.imrryr.org (chardros.imrryr.org [144.6.86.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1069DC14F5E4 for <saag@ietf.org>; Sun, 31 Mar 2024 09:29:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1711902595; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : from; bh=zxijvynvnc0elkxK/TM/N/lyZwiBUji8NyUnUpEoGxQ=; b=gSU5hrs9nsGQPobCLms/yUyHgSs+Q5BuGk5f3E1G/V5sA2ANXHinxqVR4nqZPnxI3WCx3 Us47XkofIhkr+UhzI56KZMYfMHA/0uUP6uFvWxL9lJukkGfDl3LfDPCTmGghH2nYK2W1muO oVizywoER+z3XGpXU+uCZOvVR+5Kvgc=
Received: by chardros.imrryr.org (Postfix, from userid 1000) id D3DDF92B6EF; Sun, 31 Mar 2024 12:29:55 -0400 (EDT)
Date: Sun, 31 Mar 2024 12:29:55 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: saag@ietf.org
Message-ID: <ZgmPg0qgA9stSeUo@chardros.imrryr.org>
Reply-To: saag@ietf.org
References: <755BC73B-B981-4986-B45A-E9796DCC66BC@deployingradius.com> <ME0P300MB0713122730DC9574730AC816EE382@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM> <Zgl6ejdpJNOyUja0@chardros.imrryr.org> <E1B4CCB5-202F-4087-8B56-9E7F3D73D1D0@deployingradius.com> <ZgmDLfNxV2RKSA5o@chardros.imrryr.org> <21309D5A-E824-42C7-8BAB-366AD568E9F4@deployingradius.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <21309D5A-E824-42C7-8BAB-366AD568E9F4@deployingradius.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/GosWR-woY6VMNJ_RRmPBMfgjzjQ>
Subject: Re: [saag] RADIUS is deprecating MD5
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 31 Mar 2024 16:29:33 -0000

On Sun, Mar 31, 2024 at 11:55:35AM -0400, Alan DeKok wrote:
> On Mar 31, 2024, at 11:37 AM, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
> > This does not sound like an MD5 issue, rather this is about metadata
> > leakage from RADIUS/UDP, and MD5 is mostly just collateral damage or
> > a distraction from the core issue?
> 
>   We know that MD5 is insecure.  We know that many Access-Request packets lack all integrity checks.  I've been trying to fix this issue since 2005 or so.
> 
>   Why can't we just say "yes, 1993-era protocols are bad.  Wrap them in TLS.  Move on".
> 
>   I am more than a bit surprised that there is any resistance to this effort.

I'm just trying to better understand the core issue, which seems to be
UDP more than MD5, best I can tell from the discussion so far.  Others
can speak to whether or not the deprecation is or isn't overly
disruptive relative to the benefits.

-- 
    Viktor.

v2.23.0 | Report a Bug | By Email