IETF Logo Mail Archive

Re: [Acme] ACME signature mechanics

Nico Williams <nico@cryptonector.com> Wed, 17 December 2014 22:23 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C98C1A874B for <acme@ietfa.amsl.com>; Wed, 17 Dec 2014 14:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 bt4nu8AIlFN4 for <acme@ietfa.amsl.com>; Wed, 17 Dec 2014 14:23:14 -0800 (PST)
Received: from homiemail-a67.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id A143A1A0155 for <acme@ietf.org>; Wed, 17 Dec 2014 14:23:14 -0800 (PST)
Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id 5D26027BC064; Wed, 17 Dec 2014 14:23:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=7/gvOA8npefL32 pr7DOhC1xZYwM=; b=lBfQy0zZYZ1jlY97NY/qYFhYU9XWiBfAfPPREeC498Bqnr 3qEsloVp4/pX8wKZVD/6A8gPIICftbfd2drFShwVhAE50KfWFhBBRogZVI3ao/vO NlfkCOYQLo394IlXSPeyPD/YnSvtN+dr1G5jaK/3l1clGV60i7FRLLi2nwD6Y=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPA id E973127BC05D; Wed, 17 Dec 2014 14:23:13 -0800 (PST)
Date: Wed, 17 Dec 2014 16:23:13 -0600
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Message-ID: <20141217222309.GD3241@localhost>
References: <548FF9E3.1020703@gmail.com> <CAL02cgT9iYqtX2Ui5XQYnj=yeF_QnSkKn-jE0D5d56WMzB5bBg@mail.gmail.com> <CAMm+LwjwG0dPTkByu5WZ_ev3xNxAMwunoc-A_VK4sKPSZXRYDw@mail.gmail.com> <20141217171915.GX3241@localhost> <CAMm+LwjRk_skCW4bJ607YzeVrCN71o=p4gmzy0koYty-J7L2yQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAMm+LwjRk_skCW4bJ607YzeVrCN71o=p4gmzy0koYty-J7L2yQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/acme/zFpY138f6vWyJukXXgPvmTOk4WM
Cc: Richard Barnes <rlb@ipv.sx>, "acme@ietf.org" <acme@ietf.org>, Anders Rundgren <anders.rundgren.net@gmail.com>
Subject: Re: [Acme] ACME signature mechanics
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 22:23:15 -0000

On Wed, Dec 17, 2014 at 03:28:27PM -0500, Phillip Hallam-Baker wrote:
> On Wed, Dec 17, 2014 at 12:19 PM, Nico Williams <nico@cryptonector.com>
> wrote:
> >
> > On Wed, Dec 17, 2014 at 12:02:10PM -0500, Phillip Hallam-Baker wrote:
> >
> > That does leave two open issues to be decided though:
> > >
> > > 1 Should the signature header be part of the HTTP header or the payload?
> >
> > The payload.  And then you've created a new MIME type.
> 
> 
> *message/rfc822*

I guess that works.

> In fact we could even make both the header and the payload portion JSON
> encoded and then just use the JSON list spec to put them both in the same
> wrapper. The only hard part here is that we have a sequence of octets and
> we need to unambiguously specify exactly where the dividing line is between
> them:

Might as well just have a single JSON value wrapping both (or a JSON
text sequence!), but whatever.

Nico
--

v2.23.0 | Report a Bug | By Email