Re: [Acme] ACME signature mechanics

Anders Rundgren <anders.rundgren.net@gmail.com> Tue, 30 December 2014 06:16 UTC

Return-Path: <anders.rundgren.net@gmail.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 02B6B1A1F1D for <acme@ietfa.amsl.com>; Mon, 29 Dec 2014 22:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 4a9wIE4QFGTs for <acme@ietfa.amsl.com>; Mon, 29 Dec 2014 22:16:39 -0800 (PST)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43F691A1B84 for <acme@ietf.org>; Mon, 29 Dec 2014 22:16:39 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id q59so531027wes.10 for <acme@ietf.org>; Mon, 29 Dec 2014 22:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MYjBkjbD1TmczDfsUrRqQlR3l+T7D3p0DeJCaaQKceY=; b=kT6hKUkgvPc4ZvBl8VqMt10vV+rDP+tIKKs7+3pi7+dk/sZgdr7pY40V0FFDUwyucm j1bjByljv1ja9RpR27YnJn5pRo1d3tFHVA4Pl5OkggJ1A3AENGPmz584fbQBhBx/dd3T bCYlmZ0SsMnG+3t5oMT4Glh0xVQSlB5XoEVJa7lzSChH2mM0Fda8chl9F0GtS2cOJMO1 w8nYOmSmRxii8rkeSi2f5rF1ROf+21IEMQf6jh3dIIzAfubo0sJfmWPsyu19oij8qIhA 1VFCyQqVbkt0FlpYMx1DrnkHMHQ8yZ/R08VGKhhwpGKLSyR0jNrNgDPQTWoeXHu10xVH cPcQ==
X-Received: by 10.194.108.98 with SMTP id hj2mr118417800wjb.102.1419920198068; Mon, 29 Dec 2014 22:16:38 -0800 (PST)
Received: from [192.168.1.79] (48.194.130.77.rev.sfr.net. [77.130.194.48]) by mx.google.com with ESMTPSA id la10sm22762501wjc.36.2014.12.29.22.16.37 for <acme@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Dec 2014 22:16:37 -0800 (PST)
Message-ID: <54A24341.7020104@gmail.com>
Date: Tue, 30 Dec 2014 07:16:33 +0100
From: Anders Rundgren <anders.rundgren.net@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "acme@ietf.org" <acme@ietf.org>
References: <548FF9E3.1020703@gmail.com> <CAL02cgT9iYqtX2Ui5XQYnj=yeF_QnSkKn-jE0D5d56WMzB5bBg@mail.gmail.com> <CAMm+LwjwG0dPTkByu5WZ_ev3xNxAMwunoc-A_VK4sKPSZXRYDw@mail.gmail.com> <006c01d01a33$2b086890$811939b0$@icloud.com> <CABkgnnWGQarDzpx-3f488OF2w3eyTV1iUr4GWyND+_avRHNZ6w@mail.gmail.com> <004901d01a94$55e9ebe0$01bdc3a0$@icloud.com> <54928827.9030009@gmail.com> <CAMm+Lwifqgt9e_i=froACzGW3bsY05KBiJJFBRJrqJcZrEqN8A@mail.gmail.com> <009d01d01af3$8013a2d0$803ae870$@icloud.com> <CAMm+Lwj-mN9=Dbw0-xUjhj1XUyw5NZiDQ4SaY6xcCAAy+VZTMA@mail.gmail.com>
In-Reply-To: <CAMm+Lwj-mN9=Dbw0-xUjhj1XUyw5NZiDQ4SaY6xcCAAy+VZTMA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/acme/qjzliUzlX0qZhsNRquwL-cdgKTU
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: Tue, 30 Dec 2014 06:16:51 -0000

Before you bury the ACME semantics in Base64 or settle on a HTTP-based signature
scheme it might be interesting to know that the following 130 lines of Python
represents a fully JCS-compliant RSA and EC signature validator:
https://code.google.com/p/openkeystore/source/browse/python/trunk/src/org/webpki/json/JCSValidator.py

I still haven't tried JCS on .NET but since MSFT is putting the entire foundation
as open source I don't expect this to be a major issue.

BTW, undefined object serialization order isn't exactly as popular as claimed :-)
https://code.google.com/p/v8/issues/detail?id=164

Anders