1993-10-23 - Re: ADMIN: proposed new policy on the mailing list

Header Data

From: Panzer Boy <panzer@drown.slip.andrew.cmu.edu>
To: Eric Hughes <hughes@ah.com>
Message Hash: 9db45986343741fc9cd4641360429654f4e18be4adbba2d35fb557d5c1283e6a
Message ID: <Pine.3.05.1.9310231606.C20719-a100000@drown.slip.andrew.cmu.edu>
Reply To: <9310231738.AA02831@ah.com>
UTC Datetime: 1993-10-23 20:58:26 UTC
Raw Date: Sat, 23 Oct 93 13:58:26 PDT

Raw message

From: Panzer Boy <panzer@drown.slip.andrew.cmu.edu>
Date: Sat, 23 Oct 93 13:58:26 PDT
To: Eric Hughes <hughes@ah.com>
Subject: Re: ADMIN: proposed new policy on the mailing list
In-Reply-To: <9310231738.AA02831@ah.com>
Message-ID: <Pine.3.05.1.9310231606.C20719-a100000@drown.slip.andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain


The problem that I see with this policy is that how are you going to
verify that the signature at the bottom is valid?  Anyone can generate PGP
keys pointing to anything.  Are you going to collect keys from
subscribers?  What about spoofing keys so that they apear valid, yet aren't?

I'm just curious to how this is going to be achieved.  I assume you don't
want to moderate the list (reading and approving everything).

-Matt  (panzer@drown.slip.andrew.cmu.edu)
(I would have signed this, but I lost the message on how to get pgp
to sign and leave the message in plaintext)

-------------Included Message---------------------
On Sat, 23 Oct 1993, Eric Hughes wrote:
> You will be, of course, free not to participate.  The
> rule I am considering is the following:
> 
>    Digitally sign your articles or their transmission will be delayed.
> 







Thread