[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HTTP redirectors



> One idea that was suggested here would be to have a local proxy process,
> a very simple one which your fancy client connected to for all your net
> accesses.  This would be where you would implement encryption, or new
> protocols for chaining, etc.  This way we don't have to try to persuade
> client writers to incorporate our improvements; the existing proxy
> support provides the loophole we need.  One nice feature, for example,
> would be a full 128 bit IDEA or RC4 encryption engine so that overseas
> Netscape users (or domestic ones who are stuck with crippled versions)
> can get good security.

   Indeed.  Then you could set your proxyserver to: 
http://localhost:4242/CHAIN:3/ ... which would connect to the local wedge 
on 4242, tell it to chain, and pass the URL to go to.  Hopefully then the 
wedge could pick another one out of a local list and connect to it, 
passing: CHAIN:2, ad infinitum.  It really does not seem to be very 
technically difficult.  Once again, it comes down to "who's willing to 
run these beasts?"

-jon
( --------[ Jonathan D. Cooper ]--------[ [email protected] ]-------- )
( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
( home page: http://hyperreal.com/~entropy/ ]-------[ Key-ID: 4082CCB5 )