Re: [saag] RADIUS is deprecating MD5

Alan DeKok <aland@deployingradius.com> Sun, 31 March 2024 14:25 UTC

Return-Path: <aland@deployingradius.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 248CAC14F5F1 for <saag@ietfa.amsl.com>; Sun, 31 Mar 2024 07:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ND7F_CEYIqxX for <saag@ietfa.amsl.com>; Sun, 31 Mar 2024 07:25:00 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (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 84DCFC14F5EE for <saag@ietf.org>; Sun, 31 Mar 2024 07:24:59 -0700 (PDT)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 831B21787; Sun, 31 Mar 2024 14:24:56 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <ME0P300MB0713C2E52C8DA16E3EB5DF3CEE382@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM>
Date: Sun, 31 Mar 2024 10:24:54 -0400
Cc: "saag@ietf.org" <saag@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E9599C8-13FF-4A92-B8CB-AB6C58A0AB65@deployingradius.com>
References: <755BC73B-B981-4986-B45A-E9796DCC66BC@deployingradius.com> <ME0P300MB0713122730DC9574730AC816EE382@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM> <8B488A8C-9757-47FB-8CC4-653A389CF0BE@deployingradius.com> <ME0P300MB0713C2E52C8DA16E3EB5DF3CEE382@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/v173TaDA2zBs23jxwD5uVLmZ9So>
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 14:25:03 -0000

On Mar 31, 2024, at 9:59 AM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:
> 
> Alan DeKok <aland@deployingradius.com> writes:
> 
>> Um... that is very much not what RADIUS is.
> 
> I'm not talking about RADIUS as RADIUS, I'm talking about RADIUS as a
> substrate for the next half-dozen layers up.

  The use-case you described was a very small, if not negligible one.  Both for RADIUS, and for the next few layers up.  Similarly, the comment about RADIUS being "not worth attacking" shows a misunderstanding of just how critical RADIUS is for the entire Internet.

> So it doesn't matter if, as used in that situation, RADIUS uses a Fletcher
> checksum for "security" or prepends the password to the first packet sent
> because it's acting only as a substrate for all the other layers, including
> the ones providing the security.  That's the case I mentioned, user =
> "anonymous", password = whatever (I've seen things like "anonymous",
> "password", "dummy", and others) because RADIUS isn't doing anything except
> meeting a requirement that it be present.

  I can only respond here by saying "no".

> Probably best for another thread, but if there aren't any major attacks
> against it occurring, as you mentioned previously, then it seems like
> attackers don't consider it worth attacking.

  Is it worth attacking a protocol which is in every single network switch, router, firewall, GGSN concentrator, etc. world-wide?  A protocol which, if successfully attacked, could give the attacker unfettered network access?

  I suspect that the answer to that is "yes".

  So why has no one done it?  Largely because no one cares.

  I'm not saying that I'm personally offended when people say bad things about RADIUS.  By all accounts it's a terrible protocol, and it's a bit of a miracle that it works.  I'm asking that criticisms of it be based on understanding what it is, and how it's used.

  Alan DeKok.