[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgp-keyserver-folk
Subject:    Re: "No... not THAT red button!" (was: Re: [PGP-6557]: Key serve
From:       "teun, Tilburg University" <Teun.Nijssen () kub ! nl>
Date:       1999-01-11 10:43:06
[Download RAW message or body]

Hello Michael,

/> "teun, Tilburg University" writes:
/>> If 501k keys use 1.739 Gb in the keydb file and growth is 20k keys per
/>> month, when will it die and what is the Del Torto Unit?
/>
/> This is probably not a good assumption.  My SWAG is that keyserver growth
/> is geometric not arithmetic, in fact it's probably
/> exponential.  Keys have signatures.  A lot of the increments are
/> mods to existing keys.   I don't know what the stats are on
/> this; it is true that the ratio of signature changes : new keys
/> appears to be much smaller than it was pre-PGP 5.
/
/All good points, Michael. New DH keys make far smaller sigs, perhaps 
/at least 1/2 the size (?) though they're non-deterministic due to 
/randomness.

I don't think the sigs matter too much. If you run something like

#!/bin/sh
# pksdctl /usr/users/pks/var/pksd_socket backup
pksclient /usr/users/pks/var/db/backup get x aids >pubring.pgp
op_split pubring.pgp -s 10000 /ext1/pks/rings/pub
ls -lR /ext1/pks/rings

you will see that ten thousand keys really are 10 MB. My earlier
1 kB per key average is fairly good....

/ext1/pks/rings:
total 458112
-rw-rw-rw-   1 pks      users    10995118 Jan 11 10:28 pub.000
-rw-rw-rw-   1 pks      users    10880690 Jan 11 10:28 pub.001
-rw-rw-rw-   1 pks      users    10894574 Jan 11 10:28 pub.002
-rw-rw-rw-   1 pks      users    10896275 Jan 11 10:28 pub.003
-rw-rw-rw-   1 pks      users    10823434 Jan 11 10:28 pub.004
-rw-rw-rw-   1 pks      users    10867238 Jan 11 10:28 pub.005
-rw-rw-rw-   1 pks      users    10833877 Jan 11 10:28 pub.006
-rw-rw-rw-   1 pks      users    11011595 Jan 11 10:28 pub.007
-rw-rw-rw-   1 pks      users    10914044 Jan 11 10:28 pub.008
-rw-rw-rw-   1 pks      users    10960774 Jan 11 10:28 pub.009
-rw-rw-rw-   1 pks      users    10885543 Jan 11 10:28 pub.010
-rw-rw-rw-   1 pks      users    10860467 Jan 11 10:28 pub.011
-rw-rw-rw-   1 pks      users    10902735 Jan 11 10:29 pub.012
-rw-rw-rw-   1 pks      users    10889922 Jan 11 10:29 pub.013
-rw-rw-rw-   1 pks      users    10997490 Jan 11 10:29 pub.014
-rw-rw-rw-   1 pks      users    10883709 Jan 11 10:29 pub.015
-rw-rw-rw-   1 pks      users    10876320 Jan 11 10:29 pub.016
-rw-rw-rw-   1 pks      users    10907211 Jan 11 10:29 pub.017
-rw-rw-rw-   1 pks      users    11003263 Jan 11 10:29 pub.018
-rw-rw-rw-   1 pks      users    10872653 Jan 11 10:29 pub.019
-rw-rw-rw-   1 pks      users    11019560 Jan 11 10:29 pub.020
and so on.

It is very sobering to know that modern versions of PGP sign newly
generated keys automatically with the key itself and then run

#!/bin/sh
echo 'counting public keys....'
pksclient var/db/backup index aids aids | grep '^pub' | wc -l
pksclient var/db/backup index aids aids | grep '^sig' | wc -l

Okay, first guess the average number of sigs per key and only then
run this....

cheers,

teun

[prev in list] [next in list] [prev in thread] [next in thread]