Re: establishing trust

17 Dec 2003

      -----BEGIN PGP SIGNED MESSAGE-----
...
...
From khijol!erc@uunet.uu.net Thu Nov 23 16:21 EST 1995
From: "Ed Carp [khijol SysAdmin]" <khijol!erc@uunet.uu.net>
..so..why the UUCP style address?
Because I don't have a real UUCP connection at the moment.  Khijol is 
expected to get back on the net as khijol.org in the next few days.  Just 
trying to get by until then :)
...
...
Subject: Re: crypto for porno users
To: khijol!clark.net!cme@uunet.uu.net (Carl Ellison)
Date: Thu, 23 Nov 1995 15:57:17 -0600 (CST)
Cc: khijol!got.net!edge@uunet.uu.net, khijol!toad.com!cypherpunks@uunet.uu.net
...
totally different from this "web of trust" I keep hearing about - and that is
*it*.  Do you trust me any more now than before I started signing my postings?
Actually, in my view, signed postings are the first step.  With those (and
the right S/W (not there yet)), I get to know that a bunch of postings came
from the same person.  I even know who they came from:  the person who
is capable of signing with key 0xXXXXXXXX.
Yes, but that only establishes that I was the one who wrote the post, not 
that I am to be trusted...
...
Since the only way I have of getting to know the person is through those
postings, I get to know that person and through that knowledge I decide
whether or not to trust.
And, yes, I can be fooled.
I've met a fair number of people in person that I've met over the net, and
I'm here to tell you that a lot of people I've met are totally different
in person than they are over the net.  People that I thought I could trust
gave me the willies in person, and I eventually found out that I couldn't
trust them at all.  Get burned a couple of times like that, and you learn
to suspend trust until you really meet someone in person. 

Just my $0.02.
- --
Ed Carp, N7EKG    			Ed.Carp@linux.org, ecarp@netcom.com
					214/993-3935	voicemail/pager
Finger ecarp@netcom.com for PGP 2.5 public key		an88744@anon.penet.fi

Q.	What's the trouble with writing an MS-DOS program to emulate Clinton?
A.	Figuring out what to do with the other 639K of memory.