[rtcweb] SDES and forking [was RE: RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]]

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 02 November 2011 10:54 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E17A21F9F41 for <rtcweb@ietfa.amsl.com>; Wed, 2 Nov 2011 03:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level:
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOdmOZtA6JcA for <rtcweb@ietfa.amsl.com>; Wed, 2 Nov 2011 03:54:26 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 67F8421F9F39 for <rtcweb@ietf.org>; Wed, 2 Nov 2011 03:54:26 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-cd-4eb12161b221
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 6D.FE.20773.16121BE4; Wed, 2 Nov 2011 11:54:25 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 2 Nov 2011 11:54:25 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Wed, 02 Nov 2011 11:54:23 +0100
Thread-Topic: SDES and forking [was RE: RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
Thread-Index: AcyXRuxXL0m+HvX7TS6DFejg12yLHQCBfwngAAAyLnA=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058522356F2F14@ESESSCMS0356.eemea.ericsson.se>
References: <20111024224257.28459.65554.idtracker@ietfa.amsl.com> <6EB8679A-13D5-4AD7-97F2-BC35FC0966F0@acmepacket.com> <2E239D6FCD033C4BAF15F386A979BF51159C32@sonusinmail02.sonusnet.com> <CALiegfnVaZjh1K+brd180Z9Ufheau3v6OJe6Ejv8P7wzw6ROQw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF51159D7A@sonusinmail02.sonusnet.com> <4EAAF413.8030501@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF51159D7B@sonusinmail02.sonusnet.com> <247FFE2C-DB2C-4280-A219-BE1503662F92@acmepacket.com> <4EAB2657.7090609@jesup.org> <CAD5OKxu=3FvnUDV5m1TW8n+7D+B6ihp_g7TXKtJVaVW3gtiySQ@mail.gmail.com> <4EAC24A2.70401@alvestrand.no> <4EADBAD3.5020804@mozilla.com> <7F2072F1E0DE894DA4B517B93C6A058522356F2F11@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058522356F2F11@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [rtcweb] SDES and forking [was RE: RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 10:54:27 -0000

 

If using the same keys for media assocaited with all early dialogs is a security vulnerability, that is.

> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer Holmberg
> Sent: 2. marraskuuta 2011 12:53
> To: rtcweb@ietf.org
> Subject: [rtcweb] SDES and forking [was RE: RTCWeb Forking 
> usecase [was RE: 
> draft-kaplan-rtcweb-sip-interworking-requirements-00]]
> 
> 
> Hi, 
> 
> > If we support SDES, the offer also contains crypto keys. Reusing 
> > crypto keys for all created connections would be a huge security 
> > vulnerability.
> 
> If using the same keys for media assocaited with all early 
> dialogs, one could, for each early dialog, send a new offer, 
> with dialog-specific SDES keys.
> 
> Yes, it would require a new offer, which I have previously 
> said I don't like. But, in this case, if you don't have to 
> change the local IP parameters/candidates etc, the new offer 
> would not trigger a ICE re-start etc.
> 
> Regards,
> 
> Christer
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>