From: Mike Ingle <MIKEINGLE@delphi.com>
To: cypherpunks@toad.com
Message Hash: 6c0f1f76c943d087484d88a2d65170fcc51c7b3c0144ac42b5e1fdac06cbb716
Message ID: <01HB9P5CBXDE9BZ8MR@delphi.com>
Reply To: N/A
UTC Datetime: 1994-04-17 08:42:55 UTC
Raw Date: Sun, 17 Apr 94 01:42:55 PDT
From: Mike Ingle <MIKEINGLE@delphi.com>
Date: Sun, 17 Apr 94 01:42:55 PDT
To: cypherpunks@toad.com
Subject: Key Eater Needed
Message-ID: <01HB9P5CBXDE9BZ8MR@delphi.com>
MIME-Version: 1.0
Content-Type: text/plain
Hal Finney suggests expiring old keys. The first thing we would need is a
way to clear the keyservers of such dead keys. The keyservers are already
up to 1.3 MB. Many of those keys must be long dead. In any case, the key
servers cannot just accumulate keys forever.
There is no way to know now when a key was sent to a server, so it is hard
to know when to delete it. One way would be to keep track of when new keys
are sent or updated, and delete any key which has not been updated within a
certain time, such as one year. All existing keys could be given six months
to live. Those who wanted to keep their present keys could send them again,
and others could create new ones.
The web of trust model does not lend itself easily to key expirations,
because this requires you to frequently get people to re-sign your key,
and to re-sign the keys of others. This creates the opportunity for the
"here's my new key, and I haven't got it resigned yet" attack. There
would have to be a fairly long overlap period between new and old keys,
during which time the old key signed the new key. Expirations would
complicate the system considerably.
--- Mike
Return to April 1994
Return to “Mike Ingle <MIKEINGLE@delphi.com>”