1993-11-15 - Re: Key Servers and True Names

Header Data

From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
To: ld231782@longs.lance.colostate.edu
Message Hash: 23480475b7578b6d6115a1981ea5d2de7aae789056ecc66739bcfe1e0fa87f18
Message ID: <9311152214.AA02136@anchor.ho.att.com>
Reply To: N/A
UTC Datetime: 1993-11-15 22:20:38 UTC
Raw Date: Mon, 15 Nov 93 14:20:38 PST

Raw message

From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
Date: Mon, 15 Nov 93 14:20:38 PST
To: ld231782@longs.lance.colostate.edu
Subject: Re: Key Servers and True Names
Message-ID: <9311152214.AA02136@anchor.ho.att.com>
MIME-Version: 1.0
Content-Type: text/plain


"L. Detweiler", or someone using his name, is a bit confused about
what keyservers are for - they're a convenience for making keys
readily available, and reducing the chances of getting a spoofed key.
The way to do a True Name Users Group is through key certification -
create a key called "L. Detweiler's True Name Certifier <ld@true.names.org>"
and use that key to sign keys for people who present real, non-forged
authentication papers, signed statements, or whatever credentials
you trust for demonstrating True Names.  People can add that
signature to the list of signatures they haul around on their public key.

I normally only use variants on my real name, with the exception of one
nym I use for anonymous posting, which is clearly a non-real name,
except when I'm using someone else's name for humor value,
or bogus names for junk mail reduction/identification (e.g.
Time Stewart or Junk Mail Stewart).

					John Doe

# Bill Stewart  Old address: wcs@anchor.ho.att.com AT&T Bell Labs, Holmdel, NJ
# After 10/15, NCR, 6870 Koll Center Parkway, Pleasanton CA, 94566
# Voice/Beeper 510-224-7043, Phone 510-484-6204, email bill.stewart@pleasantonca.ncr.com





Thread