Re: Authentication over HTTP

Henry Story <henry.story@bblfish.net> Tue, 16 July 2013 07:15 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35FB21E81AB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Jul 2013 00:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 8Qc9GLXoajw3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Jul 2013 00:15:37 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id A42BE21E81AD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 16 Jul 2013 00:15:35 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UyzSh-0003Su-AO for ietf-http-wg-dist@listhub.w3.org; Tue, 16 Jul 2013 07:14:15 +0000
Resent-Date: Tue, 16 Jul 2013 07:14:15 +0000
Resent-Message-Id: <E1UyzSh-0003Su-AO@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <henry.story@bblfish.net>) id 1UyzSZ-0003RM-Hi for ietf-http-wg@listhub.w3.org; Tue, 16 Jul 2013 07:14:07 +0000
Received: from mail-we0-f172.google.com ([74.125.82.172]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <henry.story@bblfish.net>) id 1UyzSY-0003Gs-L6 for ietf-http-wg@w3.org; Tue, 16 Jul 2013 07:14:07 +0000
Received: by mail-we0-f172.google.com with SMTP id q56so271687wes.3 for <ietf-http-wg@w3.org>; Tue, 16 Jul 2013 00:13:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=x5SNwxFggidCVsZbDLEMdMadYbzlRtjZmFaCG38yjTs=; b=ajLqp12Ip2/4ZzqFJABM3HAU/so0Ff2NTRhjV7vrZSeow0dQZvxq0v1FkgdkE2auZ/ XBrTfTYHg39UruCZc/R7/vxXvdZ3FOgZDR1ZeOtSBW4IIgWHc3QRC/0USsrw0FORANc0 AEy6H13BJj4Y5FCqfOYROQKekoMyjW/lsBlsIAqYz9hPSZJ9u8YQcU5C4sZ2wGzcWzIL 4nYQd0KHsqz8DHYwHDlyVoMkcaUt3+I6Fu8olD4G6xPLZkEgFzlwqFr/GbwhIkN+P+xy XWji+5xbekJ897Zkv4H1hRni8PwKDVqGwhRffdc0qY74RzYDBCote6mnGGS0FNxgO65J P/Vw==
X-Received: by 10.180.74.232 with SMTP id x8mr11198154wiv.48.1373958820509; Tue, 16 Jul 2013 00:13:40 -0700 (PDT)
Received: from bblfish.home (AAubervilliers-652-1-122-215.w90-3.abo.wanadoo.fr. [90.3.169.215]) by mx.google.com with ESMTPSA id iz8sm295901wic.3.2013.07.16.00.13.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Jul 2013 00:13:38 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Henry Story <henry.story@bblfish.net>
In-Reply-To: <CAK3OfOjeOLDHbSpcwXd9SAzDqfigxaCsTZp7LXAD6R-2oCCgtw@mail.gmail.com>
Date: Tue, 16 Jul 2013 09:13:37 +0200
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, M Stefan <mstefanro@gmail.com>, ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <75D5A854-C535-4824-8FF2-B7164A819086@bblfish.net>
References: <51E330F5.6050100@gmail.com> <19433.1373846559@critter.freebsd.dk> <CAK3OfOjeOLDHbSpcwXd9SAzDqfigxaCsTZp7LXAD6R-2oCCgtw@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQn4+kq4+ttIR34bs9aqXDgzfvlQgBXMG/GH/huLChP+8oz/9xI9T3qSUnAzT7BlPwz8u4qs
Received-SPF: none client-ip=74.125.82.172; envelope-from=henry.story@bblfish.net; helo=mail-we0-f172.google.com
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: AWL=-1.634, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7
X-W3C-Scan-Sig: maggie.w3.org 1UyzSY-0003Gs-L6 7259ff645d37739294c920f047a5f27c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Authentication over HTTP
Archived-At: <http://www.w3.org/mid/75D5A854-C535-4824-8FF2-B7164A819086@bblfish.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18799
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 16 Jul 2013, at 08:26, Nico Williams <nico@cryptonector.com> wrote:

> On Sun, Jul 14, 2013 at 7:02 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
>> Authentication should happen either in the encrypting transport
>> which moves HTTP/2.0 across (as in certificates and assymetric crypto)
>> or in the application transported inside HTTP/2.0 (as in most web-site
>> login dialogs), but HTTP/2.0 itself should not get involved:  It
>> is the wrong layer.
> 
> I agree.  Thus my proposal for RESTful authentication (with channel
> binding to TLS where available).  I don't believe user authentication
> in TLS will work out too well (it hasn't so far, and there are reasons
> why it should prove difficult; see my reply to Yoav's reply to
> Stefan).

RESTful authentication on the TLS level exists. We have been working for
it over the past 5 years, testing it over most well known languages, showing
how it works with distributed ACLs and distributed social networks. It's called 
WebID.

The latest draft are here:

 WebID overview: https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html
 WebID over TLS: https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/tls-respec.html
 a video is here: http://webid.info/

To try it out with WebAccess Control try
 
  https://github.com/stample/rww-play

Henry


> 
> Nico
> --
> 

Social Web Architect
http://bblfish.net/