1997-01-29 - Workaround for filtering/cybersitter

Header Data

From: Mark Rogaski <wendigo@pobox.com>
To: Cypherpunks <cypherpunks@toad.com>
Message Hash: 49867b75b6a5ba1eb38ac73c4ebfe24caf3e4625cf05f9398d17b075178cc0b3
Message ID: <199701292156.NAA12978@toad.com>
Reply To: N/A
UTC Datetime: 1997-01-29 21:56:53 UTC
Raw Date: Wed, 29 Jan 1997 13:56:53 -0800 (PST)

Raw message

From: Mark Rogaski <wendigo@pobox.com>
Date: Wed, 29 Jan 1997 13:56:53 -0800 (PST)
To: Cypherpunks <cypherpunks@toad.com>
Subject: Workaround for filtering/cybersitter
Message-ID: <199701292156.NAA12978@toad.com>
MIME-Version: 1.0
Content-Type: text/plain


If I had experience with Netscape plugins and spare time, I'd
try it myself.  But here's my proposed solution.  

A plugin in Netscape intercepts all requests,  encrypt the URL
with a pubkey algorithm, encode the string base64, send it as GET input to
a proxy server.

The proxy server decodes and decrypts the URL, gets the requested page,
and returns it.  This beats out URL-based filtering.

Still need to figure out the specifics of key-exchange.  If we use
40-bit encryption, it's exportable, and it still works in our threat
model (ie. we don't care if the watchers figure out the URL a few hours
later).

To beat out dropping packets with unacceptable pattern in them, we
could use an SSL-based server as the proxy.

The plugin could even have a nice little on/off switch and a list
list of available proxies.

mark

-- 
[]  Mark Rogaski                    || "Computers save time like kudzu    [] 
[]  wendigo@pobox.com               ||  prevents soil erosion."           [] 
[]  http://www.pobox.com/~wendigo/  ||           - afcasta@texas.net      []
[]  >> finger for PGP pubkey <<     ||                                    []






Thread