1996-02-07 - Re: Telecoms Bill

Header Data

From: Deranged Mutant <wlkngowl@unix.asb.com>
To: cypherpunks@toad.com
Message Hash: 34c61dfa3f014d68fc74f8a69bedf5024a378bdab03e831cd727126385567426
Message ID: <199602060748.CAA12211@bb.hks.net>
Reply To: N/A
UTC Datetime: 1996-02-07 07:07:33 UTC
Raw Date: Wed, 7 Feb 1996 15:07:33 +0800

Raw message

From: Deranged Mutant <wlkngowl@unix.asb.com>
Date: Wed, 7 Feb 1996 15:07:33 +0800
To: cypherpunks@toad.com
Subject: Re: Telecoms Bill
Message-ID: <199602060748.CAA12211@bb.hks.net>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

mark@unicorn.com ("Mark Grant, M.A. (Oxon)") wrote:
>
>Well, if "cypherpunks write code", is there any code we should be
>writing in response to this?

I'm not familiar with SSL protocols, but something that would anonymize 
web page access and keep it entirely encrypted (not just credit card or 
forms transactions) would be good.

Encrypted/truly anonymous ftp would be nice (though some folx would 
understandably have problems with truly anonymous uploads, and crypto 
export restrictions in the US could be problematic legally).

I think there is already work on encrypted telnet (stel) by the CERT/IT 
people.

On the non-net side of things, implementing encrypted BBS/communications 
and file-transfers is useful.  I'm told PGP-Phone is supposed to support 
encrypted communications/file-transfers... so a host-script language that 
enables a simple BBS would be nice.

Implementing encrypted/anonymous mailing lists is another idea.

Other ideas?



- ---
[This message has been signed by an auto-signing service.  A valid signature
means only that it has been received at the address corresponding to the
signature and forwarded.]

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Gratis auto-signing service

iQBFAwUBMRcHsioZzwIn1bdtAQHUzwGAwVy5oX7+XwznGkF+CHVXBqeI1dSMT1tt
gNIENdPUnst6bIPvGX4FigUnzEBPiNMH
=gV+C
-----END PGP SIGNATURE-----





Thread