Re: HTTP Signing
Jeffrey Yasskin <jyasskin@google.com> Sat, 23 November 2019 00:20 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 A1DDE12011D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 22 Nov 2019 16:20:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.252
X-Spam-Level:
X-Spam-Status: No, score=-10.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 inQYdwLIqhS2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 22 Nov 2019 16:20:00 -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 5CFF21200CE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 22 Nov 2019 16:20:00 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iYJ70-0001lZ-SG for ietf-http-wg-dist@listhub.w3.org; Sat, 23 Nov 2019 00:17:18 +0000
Resent-Date: Sat, 23 Nov 2019 00:17:18 +0000
Resent-Message-Id: <E1iYJ70-0001lZ-SG@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 <jyasskin@google.com>) id 1iYJ6w-0001kj-VA for ietf-http-wg@listhub.w3.org; Sat, 23 Nov 2019 00:17:14 +0000
Received: from mail-qv1-xf29.google.com ([2607:f8b0:4864:20::f29]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <jyasskin@google.com>) id 1iYJ6r-0008Hu-Si for ietf-http-wg@w3.org; Sat, 23 Nov 2019 00:17:14 +0000
Received: by mail-qv1-xf29.google.com with SMTP id n4so3621654qvq.9 for <ietf-http-wg@w3.org>; Fri, 22 Nov 2019 16:17:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LoaGiRTjacA7jB0tJ1gdHWZ19RTIIgbCYp9coskZ92Y=; b=aCMOAS7osfF2/Mk9xN8H4ZGf3sWyxOdjK5ptva5vY+Yj5kDvhxJ1FVE3B0kwn2wryZ Qw22hGvtSXEWUWaShu7xyHjTMS7DJYoZD2S4+VxyLaU0XlMcUwLGh7VC6gdp0583dfkw OtbcXpqY6OQ3hycGCG7J5WeoPomjPhuivxnviLgqspjj0HxTCwKvXAXQaDHbLnWK83AS pYSo+i4nd6f6XzFE/Yyh9bc+5mlgooi9tRlRBkFj7vwyp/F8NrzHWdD/XkDgCi4m3srM g4f0bFR7KnlGOGoKWzj2KZJz6kdiaWlPqzz9WYKk6pBGlCNkFhN6FFSrdm/LMuV/Eq6k ioYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LoaGiRTjacA7jB0tJ1gdHWZ19RTIIgbCYp9coskZ92Y=; b=stLGwS7d9X+dJZ9pad6YAyZUFmTaXYdeZGl0ZsQ+l0XrKaqqk8BwPYRYOV/+gauzug OY/zy+v6p7+ndRNTtdQywleR5Jm2tTANCMcN6FXuQtn0F3+cqjkXtEpEP8FkwO026uzx FaESCGIiFwbaSVnCXTRLYE0Tfv25eYr0ip3GxvONf3SHC2FNSc1leR5JyoRF7nUiMci1 cY3p49/JGy7BaPoB3s4Q4YdfFNZo9+vfae2fFpZMAsLT4gHlgSNC+eup1Gr3SoHjk8AM JIIhmUxQZdXWonIEyEFwPEzM13CSu8II3914kCV3X0y+T+vzzsKMAmEGrLGYrvHq6R7/ hjaQ==
X-Gm-Message-State: APjAAAXZ/AN8DH4hBGx8l0MQkDy+BR2vPdfQrzkp6t4h8tmJIQ0w08tb MZhQHitlGK4c18+WUmbonO0B2ejWpacYgV0F1/vasFKW3iU=
X-Google-Smtp-Source: APXvYqxD7972soDQVDfGypMB0bwkcAfYFBWoV3HswY+twKfFHqCtcA76VkT9MSrgT1JgFoKMKF9pC0xaVmRKWFCTi8c=
X-Received: by 2002:a0c:fa0a:: with SMTP id q10mr16071367qvn.193.1574468223300; Fri, 22 Nov 2019 16:17:03 -0800 (PST)
MIME-Version: 1.0
References: <CAChr6SwoGTULzG5jKsEbPRbzb1qK6F-sKT8ArEyQ3BA6T78YAQ@mail.gmail.com> <CAP9qbHXSAam1i=6B7mnEpPh3d-yzVOLQk2Vj25f9QNsoe0uaaw@mail.gmail.com> <3827BF1B-C7D7-45F5-833A-07CA72B64A12@amazon.com> <CAP9qbHU8wxrobYsV1sUsF9vdRAdetQ3Z8fcY-Y=sNdkLhHkYLw@mail.gmail.com> <71630A99-57CA-4AD0-A55B-1A4FD50120FF@amazon.com>
In-Reply-To: <71630A99-57CA-4AD0-A55B-1A4FD50120FF@amazon.com>
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Sat, 23 Nov 2019 08:16:52 +0800
Message-ID: <CANh-dX=t=e+JeH+D6DHzmuUg+AMbjoy=HJzYy9bKTQdHOCAOfw@mail.gmail.com>
To: "Richard Backman, Annabelle" <richanna@amazon.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000297df40597f873df"
Received-SPF: pass client-ip=2607:f8b0:4864:20::f29; envelope-from=jyasskin@google.com; helo=mail-qv1-xf29.google.com
X-W3C-Hub-Spam-Status: No, score=-24.6
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1iYJ6r-0008Hu-Si 58f4dd33fd28702caa0c4fa046b56b63
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP Signing
Archived-At: <https://www.w3.org/mid/CANh-dX=t=e+JeH+D6DHzmuUg+AMbjoy=HJzYy9bKTQdHOCAOfw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37182
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 Fri, Nov 22, 2019, 9:59 PM Richard Backman, Annabelle < richanna@amazon.com> wrote: > I think there's work to be done on message body signing, particularly for > streaming. Neither stock SigV4 nor cavage (IIUC) handles that particularly > well. A small point: please be precise about whether you need to create the body as a stream (incrementally), read it incrementally, or both. They seem to lead to very different designs. Jeffrey
- HTTP Signing Rob Sayre
- Re: HTTP Signing Roberto Polli
- Re: HTTP Signing Stephane Bortzmeyer
- Re: HTTP Signing Richard Backman, Annabelle
- Re: HTTP Signing Roberto Polli
- Re: HTTP Signing Richard Backman, Annabelle
- Re: HTTP Signing Roberto Polli
- Re: HTTP Signing Rob Sayre
- Re: HTTP Signing Jeffrey Yasskin