IETF Logo Mail Archive

Re: [rtcweb] SRTP and "marketing"

"Fabio Pietrosanti (naif)" <lists@infosecurity.ch> Thu, 29 March 2012 06:27 UTC

Return-Path: <lists@infosecurity.ch>
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 1375B21F84B4 for <rtcweb@ietfa.amsl.com>; Wed, 28 Mar 2012 23:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WNQkS0RjDzCZ for <rtcweb@ietfa.amsl.com>; Wed, 28 Mar 2012 23:27:22 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id E38F421F84B2 for <rtcweb@ietf.org>; Wed, 28 Mar 2012 23:27:21 -0700 (PDT)
Received: by eeke51 with SMTP id e51so747729eek.31 for <rtcweb@ietf.org>; Wed, 28 Mar 2012 23:27:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=s5EIbdTukwAEQbWX16uxvbF8DCeNq78kAf54WeUjmAg=; b=fnDSONg97iXTMrnYyza2Bw6ahF0Ee6WAFhqoVJVvWOLh4JT+Lz2nTAQsdKX8Zniiq1 TVX424z7cUcQaUnEc3aSARFSzrNn0P5oyzlWUE9QHY7dJulfu+7+zVBJ9kCWuLwRWhqj U9o4gMhAKjbzz2f+AUeZK7qPXy+bSdrllhtXahHSGgqGfHAFL61T3Tz1DexIn8WC13A3 qsos9asrT/uKukVer9Su1HhF4jgbD+N2GCMZHUbqqWelS3l1wSnLiwl9Pd3XumlQHtLM ++wL20QPm2mA3UuscSBi1VQTqq25UVTMeIoSokdBSEGN6jEoLcJtgTKbSkAdx7Sit2bv JI3A==
Received: by 10.213.36.8 with SMTP id r8mr2410279ebd.112.1333002440954; Wed, 28 Mar 2012 23:27:20 -0700 (PDT)
Received: from sonyvaiop13.local (93-32-184-146.ip34.fastwebnet.it. [93.32.184.146]) by mx.google.com with ESMTPS id e56sm18242833eea.11.2012.03.28.23.27.19 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Mar 2012 23:27:20 -0700 (PDT)
Sender: Fabio Pietrosanti <naif@infosecurity.ch>
Message-ID: <4F7400C7.6070605@infosecurity.ch>
Date: Thu, 29 Mar 2012 08:27:19 +0200
From: "Fabio Pietrosanti (naif)" <lists@infosecurity.ch>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
References: <4F72D6B3.40803@bbn.com> <5D67671F-417C-4C78-A560-0B16AC65E4E2@acmepacket.com> <4F73C929.9010900@mozilla.com> <CAD5OKxv_w90BsfH2unftkwxaFKN9SXR1ew16WbM26YapKNzrOQ@mail.gmail.com>
In-Reply-To: <CAD5OKxv_w90BsfH2unftkwxaFKN9SXR1ew16WbM26YapKNzrOQ@mail.gmail.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQkiwmw1jhYFLp54ZYHV0MeFyMVHD1YaRgxOHmoUd255vwntnY6FmQ2ug9M4t7sFdVDypfgP
Subject: Re: [rtcweb] SRTP and "marketing"
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: Thu, 29 Mar 2012 06:27:23 -0000

On 3/29/12 7:42 AM, Roman Shpount wrote:
> I actually believe that if sufficient
> monitoring constraints are not build into a browser (not to record but
> at least to monitor who the browser is exchanging data with and using
> what protocols), WebRTC would be simply disabled in most enterprises as
> a security risk.

Your concern would be addressed by the use of SDES-SRTP rather than
DTLS-SRTP.

SDES-SRTP would provide, in the context of WebRTC, the transport of SDES
key over HTTP(S) and so would let all existing methods for HTTP/HTTPS
inspection to works fine.

Technology for inspection of HTTP/HTTPS traffic already exists, are
widely deployed and so if we transport keying material over HTTP (with
SDES-SRTP), all Enterprises will already have their existing
infrastructure in-place.


-- 
Fabio Pietrosanti
Founder, CTO

Tel: +39 02 911930893 + ext: 907
Mobile: +39 340 1801049
E-mail: fabio.pietrosanti@privatewave.com
Skype: fpietrosanti
Linkedin: http://linkedin.com/in/secret

PrivateWave Italia S.p.A.
Via Gaetano Giardino 1 - 20123 Milano - Italy
www.privatewave.com

v2.30.2 | Report a Bug | By Email | System Status