1994-12-02 - Re: Cypherpunks@hks.net service

Header Data

From: dmandl@bear.com
To: cypherpunks@toad.com
Message Hash: 6269f44a36fb7a8e591dcb32fc229dabb3bd16f8e483984b009e5613e4c6448d
Message ID: <9412021408.AA21731@yeti.bsnet>
Reply To: N/A
UTC Datetime: 1994-12-02 14:09:31 UTC
Raw Date: Fri, 2 Dec 94 06:09:31 PST

Raw message

From: dmandl@bear.com
Date: Fri, 2 Dec 94 06:09:31 PST
To: cypherpunks@toad.com
Subject: Re: Cypherpunks@hks.net service
Message-ID: <9412021408.AA21731@yeti.bsnet>
MIME-Version: 1.0
Content-Type: text/plain


> From: cactus@bb.hks.net
> 
> The cypherpunks@hks.net service is now available.
> 
> It will sign any message sent to cypherpunks@hks.net with its (currently
> 384 bit) key and forward the signed message to cypherpunks@toad.com.

No offense, but what's the point?  What's next, automated key-signing
services?  Is this just intended to help people who can't sign easily
to get around Eric's proposed requirement?  If so, it seems like almost
an embarrassment--someone setting up a meaningless message signer to
spoof the cypherpunk server, which it does easily.  Doesn't sound too
good to me.

   --Dave.





Thread