Re: Embedded certificate image

[Stefan Santesson <stefan@xxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxx> wrote:

> Yoav Nir <ynir@xxxxxxxxxxxxxx> 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.