On Wed, 3 Feb 2010 17:16:26 -0500 grarpamp grarp...@gmail.com wrote:
passed the name to the exit node for SOCKS name-to-address resolution
Oh, I see, I missed that. For a sec I was thinking it was httpd
griping about Host:.
b) exoassist is a bad exit that inserts a web page into the
passed the name to the exit node for SOCKS name-to-address resolution
Oh, I see, I missed that. For a sec I was thinking it was httpd
griping about Host:.
b) exoassist is a bad exit that inserts a web page into the stream returned
to the client when a connection cannot be made.
That site
On Mon, 1 Feb 2010 04:51:54 -0500 downie - downgeo...@hotmail.com
wrote:
Date: Sun=2C 31 Jan 2010 22:36:11 -0600
From: benn...@cs.niu.edu
To: flamsm...@gmail.com=3b or-talk@freehaven.net
Subject: Re: client bug in 0.2.2.7-alpha and a new bad exit: exoassist
=20
On Sun=2C 31 Jan 2010
One is in the HTTP(S) header, which can indeed be stripped by privoxy.
HTTPS cannot be terminated, stripped and re-encapsulated by privoxy.
It passes straight through. I still offer a gold doubloon to anyone who knows
of a good unix TLS proxy/munger. One can dream.
tor handles a .nickname.exit
When trying to fetch a web page from www.fibrlink.net, I was surprised to
get an error page back from someplace in Australia,
That site is in Australia. And considering that that url is down right
now, and that they're fronting it with squid, who knows what all's
pooched on their end. Before
On Tue, 2 Feb 2010 22:47:46 -0500 grarpamp grarp...@gmail.com
wrote:
When trying to fetch a web page from www.fibrlink.net, I was surprised to
get an error page back from someplace in Australia,
That site is in Australia. And considering that that url is down right
now, and that they're
On Tue, 2 Feb 2010 22:21:12 -0500 grarpamp grarp...@gmail.com wrote:
One is in the HTTP(S) header, which can indeed be stripped by privoxy.
HTTPS cannot be terminated, stripped and re-encapsulated by privoxy.
It passes straight through. I still offer a gold doubloon to anyone who knows
Date: Sun, 31 Jan 2010 22:36:11 -0600
From: benn...@cs.niu.edu
To: flamsm...@gmail.com; or-talk@freehaven.net
Subject: Re: client bug in 0.2.2.7-alpha and a new bad exit: exoassist
On Sun, 31 Jan 2010 23:10:42 -0500 Flamsmark flamsm...@gmail.com
wrote:
On 31 January 2010 21:58
On Mon, 1 Feb 2010 09:49:00 -0500 Flamsmark flamsm...@gmail.com
wrote:
On 31 January 2010 23:36, Scott Bennett benn...@cs.niu.edu wrote:
I don't see it as being useful for attack if the user
only uses it to test for bad exits.
I was under the impression that the attack risk came from the
There's another bad exit on the loose. Its Nickname is exoassist,
and its fingerprint is 39A6 74F8 2BFB 0195 860C 04DD E0F3 6B60 C09D C72A.
When trying to fetch a web page from www.fibrlink.net, I was surprised to
get an error page back from someplace in Australia, beginning with The
On 31 January 2010 21:58, Scott Bennett benn...@cs.niu.edu wrote:
So it appears that a) there is a new tor client bug in 0.2.2.7-alpha
that
leaves the exoassist.exit in the name passed along from its SOCKS
listener
to the destination port.
Isn't .exit deprecated because it's a
On Sun, 31 Jan 2010 23:10:42 -0500 Flamsmark flamsm...@gmail.com
wrote:
On 31 January 2010 21:58, Scott Bennett benn...@cs.niu.edu wrote:
So it appears that a) there is a new tor client bug in 0.2.2.7-alpha
that
leaves the exoassist.exit in the name passed along from its SOCKS
12 matches
Mail list logo
