IETF Logo Mail Archive

Re: HTTP Signing

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 22 November 2019 10:22 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 A6D38120815 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 22 Nov 2019 02:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level:
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pISmZIM83pZA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 22 Nov 2019 02:22:23 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05F231207FD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 22 Nov 2019 02:22:23 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iY634-00011m-QK for ietf-http-wg-dist@listhub.w3.org; Fri, 22 Nov 2019 10:20:22 +0000
Resent-Date: Fri, 22 Nov 2019 10:20:22 +0000
Resent-Message-Id: <E1iY634-00011m-QK@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <bortzmeyer@nic.fr>) id 1iY632-0000z1-GE for ietf-http-wg@listhub.w3.org; Fri, 22 Nov 2019 10:20:20 +0000
Received: from mx4.nic.fr ([2001:67c:2218:2::4:12]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <bortzmeyer@nic.fr>) id 1iY630-0007sH-UG for ietf-http-wg@w3.org; Fri, 22 Nov 2019 10:20:20 +0000
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id DB79C280154; Fri, 22 Nov 2019 11:20:14 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id D558F280641; Fri, 22 Nov 2019 11:20:14 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id CE16A280154; Fri, 22 Nov 2019 11:20:14 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C3D8F6A9F3A0; Fri, 22 Nov 2019 11:20:14 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 5882D3FFD9; Fri, 22 Nov 2019 11:20:14 +0100 (CET)
Date: Fri, 22 Nov 2019 11:20:14 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Rob Sayre <sayrer@gmail.com>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Message-ID: <20191122102014.GA14311@nic.fr>
References: <CAChr6SwoGTULzG5jKsEbPRbzb1qK6F-sKT8ArEyQ3BA6T78YAQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAChr6SwoGTULzG5jKsEbPRbzb1qK6F-sKT8ArEyQ3BA6T78YAQ@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 10.1
X-Kernel: Linux 4.19.0-6-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.11.5.63017
Received-SPF: pass client-ip=2001:67c:2218:2::4:12; envelope-from=bortzmeyer@nic.fr; helo=mx4.nic.fr
X-W3C-Hub-Spam-Status: No, score=-8.5
X-W3C-Hub-Spam-Report: BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1iY630-0007sH-UG 6bdded7a49a35eb800fe05f9607a3185
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP Signing
Archived-At: <https://www.w3.org/mid/20191122102014.GA14311@nic.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37172
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Thu, Nov 21, 2019 at 10:02:09PM -0800,
 Rob Sayre <sayrer@gmail.com> wrote 
 a message of 46 lines which said:

> I saw the "HTTP Signing" presentation in the SECDISPATCH meeting on
> YouTube[1] <https://www.youtube.com/watch?v=CYBhLQ0-fwE>.

For the record, this starts at 49:50.

Note that draft-cavage-http-signatures, which he mentioned, is both
implemented and widely deployed (fediverse software, such as Mastodon,
Pleroma, PeerTube, PixelFed, etc).

v2.23.0 | Report a Bug | By Email