Re: [Sip-security] RE: SIP authentication problem when using RES in Digest-AKA

Jari Arkko <jari.arkko@kolumbus.fi> Sun, 31 March 2002 06:01 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11840 for <sip-security-archive@odin.ietf.org>; Sun, 31 Mar 2002 01:01:40 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA28594 for sip-security-archive@odin.ietf.org; Sun, 31 Mar 2002 01:01:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA28582; Sun, 31 Mar 2002 01:01:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA28549 for <sip-security@optimus.ietf.org>; Sun, 31 Mar 2002 01:01:01 -0500 (EST)
Received: from p2.piuha.net (p2.piuha.net [131.160.192.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11823 for <sip-security@ietf.org>; Sun, 31 Mar 2002 01:00:56 -0500 (EST)
Received: from kolumbus.fi (p4.piuha.net [131.160.192.4]) by p2.piuha.net (Postfix) with ESMTP id 263416A904; Sun, 31 Mar 2002 09:00:52 +0300 (EEST)
Message-ID: <3CA69865.8080508@kolumbus.fi>
Date: Sun, 31 Mar 2002 08:02:29 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011014
X-Accept-Language: en-us
MIME-Version: 1.0
To: Greg Rose <ggr@qualcomm.com>
Cc: John W Noerenberg II <jwn2@qualcomm.com>, aki.niemi@nokia.com, James Undery <jundery@ubiquity.net>, sip-security@ietf.org, torvive <torvive@hotmail.com>, vesa.torvinen@ericsson.fi, Sanjoy Sen <sanjoy@nortelnetworks.com>
Subject: Re: [Sip-security] RE: SIP authentication problem when using RES in Digest-AKA
References: <4.3.1.2.20020318120008.01ac4fb8@127.0.0.1> <4.3.1.2.20020319073002.01ae0438@127.0.0.1> <4.3.1.2.20020319141758.01b38940@127.0.0.1> <a05101504b8ca549bfbe7@[129.46.77.186]> <v04210129b8cc26e4b3f0@[203.30.171.36]>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-security-admin@ietf.org
Errors-To: sip-security-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Security Issues for the SIP protocol <sip-security.ietf.org>
X-BeenThere: sip-security@ietf.org
Content-Transfer-Encoding: 7bit

Greg Rose wrote:


>> Has anyone determined whether or not a 128-bit RES is backward 
>> compatible?
> 
> Definitely not backward compatible, although that might not yet be a big 
> deal. In the meantime, however, the vote in SA3 has been to go with 
> IPsec for integrity protection, so the problem is now moot; 32-bit RES 
> is sufficient in that context.


As far as I understand, whether IPsec or James' enhanced digest was adopted
as the solution for first hop integrity protection does not affect the RES
discussion at all. Both use the generated session key, IK, and not RES.

The only discussion has been on whether Digest AKA -- the home authentication
scheme for 3G networks -- uses RES in the clear or whether it ties the RES to the
rest of the message using MD5. The former approach is kind of like basic using
one time passwords, the latter is regular digest usage. The former is always
vulnerable to someone replacing the message contents but keeping RES; the
latter is not vulnerable to this except when RES is short.

The input from the IETF meeting was that the Digest approach is favored.

Jari


_______________________________________________
Sip-security mailing list
Sip-security@ietf.org
https://www1.ietf.org/mailman/listinfo/sip-security