Re: [hybi] On TLS-only Approaches

Adam Barth <ietf@adambarth.com> Mon, 23 August 2010 04:06 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 378E23A67E3 for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 21:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.122
X-Spam-Level:
X-Spam-Status: No, score=-2.122 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78PGh90n2ysu for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 21:06:13 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 4A3FA3A67E2 for <hybi@ietf.org>; Sun, 22 Aug 2010 21:06:13 -0700 (PDT)
Received: by gxk20 with SMTP id 20so2294926gxk.31 for <hybi@ietf.org>; Sun, 22 Aug 2010 21:06:46 -0700 (PDT)
Received: by 10.100.46.17 with SMTP id t17mr4619871ant.237.1282536406561; Sun, 22 Aug 2010 21:06:46 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id q7sm10010463anf.26.2010.08.22.21.06.44 (version=SSLv3 cipher=RC4-MD5); Sun, 22 Aug 2010 21:06:45 -0700 (PDT)
Received: by iwn3 with SMTP id 3so5905192iwn.31 for <hybi@ietf.org>; Sun, 22 Aug 2010 21:06:44 -0700 (PDT)
Received: by 10.231.30.68 with SMTP id t4mr720116ibc.129.1282536404165; Sun, 22 Aug 2010 21:06:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.187.218 with HTTP; Sun, 22 Aug 2010 21:06:14 -0700 (PDT)
In-Reply-To: <A8694FF9-334D-42D9-ADDB-6AC23890F9DA@apple.com>
References: <AANLkTikJcbyEZ-Y0FOXni89L8Awa_UBmMMDvLgsOuoou@mail.gmail.com> <AANLkTin3r+f1Fn_X5O401PSANRrcgttLR-P4qMJZWKtV@mail.gmail.com> <A8694FF9-334D-42D9-ADDB-6AC23890F9DA@apple.com>
From: Adam Barth <ietf@adambarth.com>
Date: Sun, 22 Aug 2010 21:06:14 -0700
Message-ID: <AANLkTikGpjYXVMt6qHV3gxX5bf_ggGs3J3p=29Rk75pd@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Server-Initiated HTTP <hybi@ietf.org>
Subject: Re: [hybi] On TLS-only Approaches
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Aug 2010 04:06:14 -0000

On Sun, Aug 22, 2010 at 8:47 PM, Maciej Stachowiak <mjs@apple.com> wrote:
> 3) I would guess the challenge for embedded devices that *do* want to
> provide WebSocket services is that they can't practically ship with a valid
> certificate. To address this without creating security holes, we would
> likely need two URI schemes (ws: and wss:) with two different NPN protocol
> identifiers. ws: would not require a valid cert, wss: would. The reason two
> different NPN protocol identifiers are required is to prevent
> man-in-the-middle attacks against wss: services accessed using ws: by making
> it impossible to access them via ws:.

Yeah, I agree that we'll probably still want two security levels, one
that resists active network attackers and one that doesn't.

Adam