IETF Logo Mail Archive

Re: Embedded certificate image

Stefan Santesson <stefan@aaa-sec.com> Thu, 30 July 2009 06:54 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 532873A6AC5 for <ietfarch-pkix-archive@core3.amsl.com>; Wed, 29 Jul 2009 23:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[AWL=0.699, 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 3-heTmud4uns for <ietfarch-pkix-archive@core3.amsl.com>; Wed, 29 Jul 2009 23:54:46 -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 4315D3A68A3 for <pkix-archive@ietf.org>; Wed, 29 Jul 2009 23:54:45 -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 n6U6R8ok030824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jul 2009 23:27:08 -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 n6U6R83U030822; Wed, 29 Jul 2009 23:27:08 -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 n6U6Qsv6030801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-pkix@imc.org>; Wed, 29 Jul 2009 23:27:06 -0700 (MST) (envelope-from stefan@aaa-sec.com)
Received: (qmail 853 invoked from network); 30 Jul 2009 06:26:55 -0000
Received: from s34.loopia.se (HELO s42.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 06:26:55 -0000
Received: (qmail 71957 invoked from network); 30 Jul 2009 06:26:53 -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 s42.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <ynir@checkpoint.com>; 30 Jul 2009 06:26:53 -0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 30 Jul 2009 08:26:52 +0200
Subject: Re: Embedded certificate image
From: Stefan Santesson <stefan@aaa-sec.com>
To: Yoav Nir <ynir@checkpoint.com>, 'Peter Gutmann' <pgut001@cs.auckland.ac.nz>, "ietf-pkix@imc.org" <ietf-pkix@imc.org>
Message-ID: <C69709CC.39E1%stefan@aaa-sec.com>
Thread-Topic: Embedded certificate image
Thread-Index: AcoQzZGvN8aL9aguS4C+fXwW7SsvSwAAFqlAAAQzYCo=
In-Reply-To: <006FEB08D9C6444AB014105C9AEB133F855207C898@il-ex01.ad.checkpoint.com>
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>

Exactly


On 09-07-30 6:26 AM, "Yoav Nir" <ynir@checkpoint.com> wrote:

> 
> I guess that if the image is embedded in the URL, you don't really need to
> follow it, just process it locally.
> 
> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On
> Behalf Of Peter Gutmann
> Sent: Thursday, July 30, 2009 7:10 AM
> To: ietf-pkix@imc.org; stefan@aaa-sec.com
> Subject: Re: Embedded certificate image
> 
> 
> Stefan Santesson <stefan@aaa-sec.com> writes:
> 
>> It seems that there are ways to store base64 encoded data in a URL. Since all
>> images are located through a URL, this opens interesting possibilities if the
>> URL actually contains the image data itself.
> 
> How big are these things going to get?  Anything beyond about 1024 characters
> and you start running into problems with things that reject over-long URLs.
> 
> Peter.
> 
> 
> Email secured by Check Point
>

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