Re: [hybi] About authentication mechanism

Iñaki Baz Castillo <ibc@aliax.net> Tue, 28 June 2011 22:19 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3528A21F8671 for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 15:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zVkNP3RR1Qhh for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 15:19:55 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id A55DA21F8660 for <hybi@ietf.org>; Tue, 28 Jun 2011 15:19:55 -0700 (PDT)
Received: by qwc23 with SMTP id 23so529655qwc.31 for <hybi@ietf.org>; Tue, 28 Jun 2011 15:19:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.23.69 with SMTP id q5mr41622qcb.249.1309299595085; Tue, 28 Jun 2011 15:19:55 -0700 (PDT)
Received: by 10.229.240.15 with HTTP; Tue, 28 Jun 2011 15:19:55 -0700 (PDT)
In-Reply-To: <CABLsOLD-EWb=pQ33c9FSU3cu0JTGS5mc2-e5-oq-skfp7rzQhA@mail.gmail.com>
References: <BANLkTinerv=Ua4d-ma+uPVJjF95U1U5iXg@mail.gmail.com> <BANLkTin4mWJgQm+pfyYRs_RhRkdMBfY_Og@mail.gmail.com> <BANLkTiksptqmTWftg7Ur98QQnp22QV7OLA@mail.gmail.com> <BANLkTimw8T4pZieBeCjaPQJ8oYWfbTjkmg@mail.gmail.com> <BANLkTikOzzHF1dGz-2-UwTC0kb2ZQd_0Jw@mail.gmail.com> <BANLkTimCTTCU4UFA7JFuBvDZSFv++UyGCA@mail.gmail.com> <BANLkTinWnTxkCh9BM_utX0=pxzE02DypuA@mail.gmail.com> <BANLkTi=LEOyhagpGZF9gTyLxGuqv5U64wmO_afwaw=eR=pVcPw@mail.gmail.com> <BANLkTinGb38bLyH20Q-QaP2jeDCfgYvENw@mail.gmail.com> <CABLsOLD-EWb=pQ33c9FSU3cu0JTGS5mc2-e5-oq-skfp7rzQhA@mail.gmail.com>
Date: Wed, 29 Jun 2011 00:19:55 +0200
Message-ID: <CALiegfnfWwqtWqHZ5GUCWMNdWODnV+fHNhn+fxpL49KQ=Fs8Fw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: John Tamplin <jat@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org, Greg Wilkins <gregw@intalio.com>
Subject: Re: [hybi] About authentication mechanism
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 28 Jun 2011 22:19:56 -0000

2011/6/28 John Tamplin <jat@google.com>om>:
> Note that cookies are problematic for supporting multiple tabs logged in
> with different accounts, and are vulnerable to XSRF attacks without
> additional precautions.

But still Cookies are the only authentication mechanism mentioned in
the WS draft.



> The point is common practice in web apps is not to use HTTP authentication
> anyway (aside from not being able to style it the way you want, you can't
> easily log out, plus other limitations),

I agree. It's ugly.


> but to have the app request the
> credentials and send them to the server itself.  If it takes that approach,
> then it can easily do the same thing for WS communication.

Humm, in my previous mail I already explained that a web server
returns an HTML page in which the user can fill his credentials and
so. But in WebSocket, how to do that? when you connect to a WebSocket
server you don't receive a custom HTML or a form to login.



-- 
Iñaki Baz Castillo
<ibc@aliax.net>