From erik at datenzone.de  Mon Apr 16 07:59:20 2012
From: erik at datenzone.de (Erik Tews)
Date: Mon, 16 Apr 2012 16:59:20 +0200
Subject: [Sovereign Keys] Parameters for a hash tree
Message-ID: <1334588360.6818.9.camel@lap19.cdc.informatik.tu-darmstadt.de>

Hi

I did some calculations how one could build a hash tree to verify that a
response from a mirror is really correct and based on a current database
from a timeline server. I pushed some notes to github:

https://github.com/eriktews/Sovereign-Keys/commit/f1983f6ad810c7c28fa27041d6bf710d2f1e0cca

And you can find a google docs spreadsheet online where you can play a
bit with the parameters:

https://docs.google.com/spreadsheet/ccc?key=0Ak_UqCvQqMRAdGVMTU9KRVZLQUFKUENyZzdfYUkzUEE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.eff.org/pipermail/sovereign-keys/attachments/20120416/f858c2fa/attachment.sig>

From benl at google.com  Fri Apr 20 08:16:17 2012
From: benl at google.com (Ben Laurie)
Date: Fri, 20 Apr 2012 16:16:17 +0100
Subject: [Sovereign Keys] Parameters for a hash tree
In-Reply-To: <1334588360.6818.9.camel@lap19.cdc.informatik.tu-darmstadt.de>
References: <1334588360.6818.9.camel@lap19.cdc.informatik.tu-darmstadt.de>
Message-ID: <CABrd9SRj1=joQV77Zf0sSf542ztGp_i_A_nTzxR_U-ptWAUw8Q@mail.gmail.com>

On 16 April 2012 15:59, Erik Tews <erik at datenzone.de> wrote:
> Hi
>
> I did some calculations how one could build a hash tree to verify that a
> response from a mirror is really correct and based on a current database
> from a timeline server. I pushed some notes to github:
>
> https://github.com/eriktews/Sovereign-Keys/commit/f1983f6ad810c7c28fa27041d6bf710d2f1e0cca
>
> And you can find a google docs spreadsheet online where you can play a
> bit with the parameters:
>
> https://docs.google.com/spreadsheet/ccc?key=0Ak_UqCvQqMRAdGVMTU9KRVZLQUFKUENyZzdfYUkzUEE

FWIW, I did a similar calculation for CT:
http://www.certificate-transparency.org/sizes.