Re: [pkix] EST-02. Re: status update

Wan-Teh Chang <wtc@google.com> Fri, 12 August 2011 18:11 UTC

Return-Path: <wtc@google.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D7AD21F86DC for <pkix@ietfa.amsl.com>; Fri, 12 Aug 2011 11:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 E6O9z01EcdWi for <pkix@ietfa.amsl.com>; Fri, 12 Aug 2011 11:11:18 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBED21F86B9 for <pkix@ietf.org>; Fri, 12 Aug 2011 11:11:17 -0700 (PDT)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [172.25.149.14]) by smtp-out.google.com with ESMTP id p7CIBrgB015921 for <pkix@ietf.org>; Fri, 12 Aug 2011 11:11:53 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1313172713; bh=kj4eiyuUmPbM9A3TtuqKCHfB5Iw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=Xmgdw/mX7MbM3SQT3D5g8hvZirwOp5zBDGCaslta2B7VaYrxwvwR+bZS3u9tolLd8 HJ7qCG7cn8fCE2sIOdrHw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=jP+J4eNUHGnT0ypvv+Xy/X0i3XAfcZNILsSsfBcKz/vDbB8C9zQLfhFi5gtGDEsVO fA3MRlpuBOkLHOhHGKkYw==
Received: from iym1 (iym1.prod.google.com [10.241.52.1]) by hpaq14.eem.corp.google.com with ESMTP id p7CIA2uB018564 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <pkix@ietf.org>; Fri, 12 Aug 2011 11:11:51 -0700
Received: by iym1 with SMTP id 1so2068850iym.0 for <pkix@ietf.org>; Fri, 12 Aug 2011 11:11:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NN6Cv3baZKZjtWEaB+xXfISYSDzfJywWJ+1qcKhGUg4=; b=PnENOLSu0vqb0Uyx/klKNPg85ix0H3hMzfBWFCmN6+RNIaPRVo6e57sYS+/KNRjsZJ rYj9u03o9KPhQnNK5fpQ==
Received: by 10.42.151.2 with SMTP id c2mr1283670icw.15.1313172711196; Fri, 12 Aug 2011 11:11:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.151.2 with SMTP id c2mr1283662icw.15.1313172711112; Fri, 12 Aug 2011 11:11:51 -0700 (PDT)
Received: by 10.231.14.70 with HTTP; Fri, 12 Aug 2011 11:11:51 -0700 (PDT)
In-Reply-To: <4E456093.6090609@telia.com>
References: <p0624080fca689135cceb@128.89.89.43> <4E437E9D.8000504@telia.com> <p06240801ca69b700066b@192.168.1.13> <328D52E9-2105-4E66-A7BC-B7DCFE495A08@cisco.com> <4E456093.6090609@telia.com>
Date: Fri, 12 Aug 2011 11:11:51 -0700
Message-ID: <CALTJjxE_cP99EACvwNwe9tzVoK8uR5RgTUvbWah=d3MOysSxng@mail.gmail.com>
From: Wan-Teh Chang <wtc@google.com>
To: Max Pritikin <pritikin@cisco.com>, Anders Rundgren <anders.rundgren@telia.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: pkix@ietf.org
Subject: Re: [pkix] EST-02. Re: status update
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 18:11:19 -0000

On Fri, Aug 12, 2011 at 10:19 AM, Anders Rundgren
<anders.rundgren@telia.com> wrote:
> On 2011-08-12 19:04, Max Pritikin wrote:
>
>> There is nothing within EST or CMC or SCEP or otherwise that
>> would _preclude_ a browser or a mobile device.
>
> That's what the KEYPROV guys said as well.  However, they forgot
> a tiny detail: how to bind their protocol to a browser.

I am interested in implementing a certificate enrollment protocol in
Firefox and Google Chrome to replace <keygen>.  I am studying
KeyGen2 and EST.  I have a question about Anders' comment
above.

By "binding a certificate enrollment protocol to a browser", do you
mean specifying an HTML element or JavaScript function for a
server to kick off the key generation and certificate request
generation in the browser?

For importing a newly issued certificate into a browser, draft-pritikin-est-02
specifies the MIME-type "application/x-est-x509" for the HTTP
response carrying the new certificate, which is the moral equivalent
of "application/x-x509-user-cert" used for <keygen>.  So it's not
clear to me if any other "browser binding" is necessary for this
operation.  Perhaps a JavaScript function similar to Mozilla's
crypto.importUserCertificates function?
https://developer.mozilla.org/en/JavaScript_crypto/importUserCertificates

The handling of an HTTP 202 response in Section 5.2.2 of
draft-pritikin-est-02 does seem to be intended for an automated
client (such as one running on an unattended network
appliance) rather than a web browser.

Wan-Teh Chang