IETF Logo Mail Archive

Re: Embedded certificate image

Stefan Santesson <stefan@aaa-sec.com> Thu, 30 July 2009 08:14 UTC

Return-Path: <owner-ietf-pkix@mail.imc.org>
X-Original-To: ietfarch-pkix-archive@core3.amsl.com
Delivered-To: ietfarch-pkix-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A141028C1CD for <ietfarch-pkix-archive@core3.amsl.com>; Thu, 30 Jul 2009 01:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.783
X-Spam-Level:
X-Spam-Status: No, score=-1.783 tagged_above=-999 required=5 tests=[AWL=0.466, BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8PcqH037Yor5 for <ietfarch-pkix-archive@core3.amsl.com>; Thu, 30 Jul 2009 01:14:32 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id D7F5028C15C for <pkix-archive@ietf.org>; Thu, 30 Jul 2009 01:13:42 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6U7iauw036115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jul 2009 00:44:36 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n6U7iaQx036114; Thu, 30 Jul 2009 00:44:36 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6U7iXYI036103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-pkix@imc.org>; Thu, 30 Jul 2009 00:44:35 -0700 (MST) (envelope-from stefan@aaa-sec.com)
Received: (qmail 24732 invoked from network); 30 Jul 2009 07:44:34 -0000
Received: from s34.loopia.se (HELO s60.loopia.se) ([194.9.94.70]) (envelope-sender <stefan@aaa-sec.com>) by s87.loopia.se (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for <ietf-pkix@imc.org>; 30 Jul 2009 07:44:34 -0000
Received: (qmail 57861 invoked from network); 30 Jul 2009 07:44:31 -0000
Received: from static-88.131.106.162.addr.tdcsong.se (HELO [10.133.3.238]) (stefan@fiddler.nu@[88.131.106.162]) (envelope-sender <stefan@aaa-sec.com>) by s60.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <pgut001@cs.auckland.ac.nz>; 30 Jul 2009 07:44:31 -0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 30 Jul 2009 09:44:30 +0200
Subject: Re: Embedded certificate image
From: Stefan Santesson <stefan@aaa-sec.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>, ietf-pkix@imc.org, ynir@checkpoint.com
Message-ID: <C6971BFE.39EC%stefan@aaa-sec.com>
Thread-Topic: Embedded certificate image
Thread-Index: AcoQ6ZI3cP7DeB3yD0a6BwVTdwKfhw==
In-Reply-To: <E1MWQBi-0002jI-Ae@wintermute01.cs.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>

Good question.

The reason would be to allow data to be stored locally when the original
specification only offers the option to specify a URL to the location of the
data.

This is the case for RFC 3709, which is the standard we would use to bind a
cert image to the certificate. RFC 3709 does only offer a URL as means of
referring to the actual image, it does not offer any other means of local
storage.

By providing the image in the URL, we could offer a way to embed the image
and still stay within the syntax of the original spec.

/Stefan


On 09-07-30 9:36 AM, "Peter Gutmann" <pgut001@cs.auckland.ac.nz> wrote:

> Yoav Nir <ynir@checkpoint.com> writes:
> 
>> I guess that if the image is embedded in the URL, you don't really need to
>> follow it, just process it locally.
> 
> In that case why encode it as a URL in the first place?
> 
> Peter.

v2.46.0 | Report a Bug | By Email | System Status