From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
To: cypherpunks@toad.com
Message Hash: a89c8faefaead208eec57012c610e5e8c2fa1350b4aaa1fa577f6440c88796e8
Message ID: <9403022140.AA22586@anchor.ho.att.com>
Reply To: N/A
UTC Datetime: 1994-03-02 21:41:49 UTC
Raw Date: Wed, 2 Mar 94 13:41:49 PST
From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
Date: Wed, 2 Mar 94 13:41:49 PST
To: cypherpunks@toad.com
Subject: Re: Insecurity of public key crypto #1 (reply to Mandl)
Message-ID: <9403022140.AA22586@anchor.ho.att.com>
MIME-Version: 1.0
Content-Type: text/plain
A while back, when people were starting to talk about encrypting the
list, someone like Eric Hughes pointed out that, if you *want*
to run an encrypted, or batch-digested, or whatever, version of
cypherpunks, you were free to do so - just set up your system
and have it forward cypherpunks to your subscribers.
Somebody could still do it now (not me! :-), preferably outside the
US where the problems of RSA/PKP patents don't apply.
The flip side of the problem is building an automagic decryptor
for mail sent *to* cypherpunks, though you could accomplish part
of that by using the extropia anonymous remailer which accepts
encrypted mail.
On the other hand, doing either of these functions on toad.com today
risks subjecting John and friends to harassment from RSA
(unless toad.com happens to be a Sun 486i or really hot box with
SoftPC that can emulate Intel code fast enough to run ViaCrypt.)
Bill
Return to March 1994
Return to “wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)”
1994-03-02 (Wed, 2 Mar 94 13:41:49 PST) - Re: Insecurity of public key crypto #1 (reply to Mandl) - wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)