-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 15 Jun 1998, William H. Geiger III wrote:
I am not quite sure what you mean by serial number and how it relates to
insuring that two DB's have the same key?
A serial number is an ID for each PGP-Packet (i.e. pubkey, sigs, revocs
etc). Its main purpose is to ensure that all keyservers taking part on
this "KBone" have received all updates.
If we are talking about a end users how does he insure that his local
copy of a key is the same as the servers without periodically
downloading the keys?
In normal operation the PGP-Packets containing the serial numbers are not
exported. I only suggested that one could use these serial numbers for
this. This is not fully thought through yet, but imagine a function which
takes serial numbers as paramter and returns the updates which are not
covered by those.
A more realistic possibility would be a local keyserver
which receives incrementals (only updates, not whole keys) and stores only
interesting ones (e.g. all with your.sub.domain on the userid).
Michael Baumer, Praesident VIS
VIS - Verein der Informatikstudierenden an der ETH Zuerich
e-mail (pers.): baumi(_at_)vis(_dot_)inf(_dot_)ethz(_dot_)ch
e-mail (Verein): vis(_at_)vis(_dot_)inf(_dot_)ethz(_dot_)ch
PGP-KeyID: 2238F089, 2048 Bits
finger baumi(_at_)neelix(_dot_)ethz(_dot_)ch for pgp-key
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----