Re: [http-auth] First draft of HTTP Signatures published

Yoav Nir <ynir@checkpoint.com> Sun, 12 May 2013 03:37 UTC

Return-Path: <ynir@checkpoint.com>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F398621F89E2 for <http-auth@ietfa.amsl.com>; Sat, 11 May 2013 20:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.45
X-Spam-Level:
X-Spam-Status: No, score=-10.45 tagged_above=-999 required=5 tests=[AWL=0.149, 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 MlwlTqhB7KZ1 for <http-auth@ietfa.amsl.com>; Sat, 11 May 2013 20:37:32 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 67E7221F8916 for <http-auth@ietf.org>; Sat, 11 May 2013 20:37:32 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4C3bELu002325; Sun, 12 May 2013 06:37:14 +0300
X-CheckPoint: {518F0CA3-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Sun, 12 May 2013 06:37:13 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Thread-Topic: [http-auth] First draft of HTTP Signatures published
Thread-Index: AQHOTaxcGLfKsfPu0kKEZwtLkyHGXJkAtmaA
Date: Sun, 12 May 2013 03:37:12 +0000
Message-ID: <14CD3EC8-7302-4D8E-8575-1400352C7465@checkpoint.com>
References: <518D3C8B.3080807@digitalbazaar.com>
In-Reply-To: <518D3C8B.3080807@digitalbazaar.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.20.52]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11ae384d0ef537865dd8b98ce38c3c05c299b36930
Content-Type: text/plain; charset="us-ascii"
Content-ID: <002B8F745C37AF4195BC6A17C9169884@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: HTTP Auth WG <http-auth@ietf.org>
Subject: Re: [http-auth] First draft of HTTP Signatures published
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-auth>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 May 2013 03:37:37 -0000

Hi Manu

The HTTP-Auth working group is chartered to work on a very specific set of documents. OTOH, the WebSec working group is considering adopting a work item for session continuation. Session continuation is supposed to be a replacement for authorizing requests via session cookies. See the problem statement here:

http://tools.ietf.org/html/draft-williams-websec-session-continue-prob-00

If I understand correctly, your draft is aiming to solve that issue. So you might prefer to take your draft there.

Yoav Nir (as co-chair of both groups)

On May 10, 2013, at 9:29 PM, Manu Sporny <msporny@digitalbazaar.com> wrote:

> The HTTP Signatures spec is a digital signature mechanism for the HTTP
> protocol. It adds origin authentication, message integrity, and replay
> resistance to HTTP requests. This is useful for any application that
> currently depends on Basic, Digest, OAuth, or OAuth2 authentication when
> performing RESTful HTTP calls.
> 
> Basically, if a client needs to prove to a server that it sent an
> HTTP-based message, it can digitally sign that message. This spec
> defines exactly how that happens.
> 
> This spec will be used by the Web Payments / PaySwarm / Web Keys work at
> W3C. We're going to combine the public/private key-based signature
> mechanism defined in HTTP Signatures with the public key infrastructure
> system as defined in Web Keys to provide an easy way for nodes on the
> Internet to verify their identity to other nodes on the Internet.
> 
> The first draft of this spec was just published via the Internet
> Engineering Task Force (IETF) earlier today:
> 
> http://tools.ietf.org/html/draft-cavage-http-signatures-00
> 
> You can also find a datetime-stamped version of the spec here:
> 
> https://payswarm.com/specs/ED/http-signatures/2013-05-04/
> 
> The latest version of the spec can be found on the PaySwarm specs page:
> 
> https://payswarm.com/specs/
> 
> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Meritora - Web payments commercial launch
> http://blog.meritora.com/launch/
> _______________________________________________
> http-auth mailing list
> http-auth@ietf.org
> https://www.ietf.org/mailman/listinfo/http-auth
> 
> Email secured by Check Point