> tl;dr Did you by any chance compile tor with bufferevents enabled
> (--enable-bufferevents)?
Yes, I did.
> Let's see the path of the sent bytes string:
Thanks for that explanation!
Sebastian
___
tor-talk mailing list
tor-talk@lists.torproject.o
The following error message appeared in the Message Log;
Oct 01 10:09:01.783 [Warning] Requested exit point '$SOME REALLY HUGE
NUMBER' is excluded or would refuse request. Closing.
Oct 01 10:09:02.356 [Warning] Making tunnel to dirserver failed.
Should I be concerned about it? What does it mea
On 11/3/2011 3:53 AM, Advrk Aplmrkt wrote:
On 2 November 2011 20:17, Julian Yon wrote:
As the GPL is one of the license options, there is no way that any
contract or agreement between Google and Mozilla could possibly be
binding on a third party. Mozilla do impose restrictions on use of their
Sebastian Lechte wrote:
> > tl;dr Did you by any chance compile tor with bufferevents enabled
> > (--enable-bufferevents)?
>
> Yes, I did.
>
I see.
We've noticed this issue some months ago with bufferevents enabled,
but it's not easy to reproduce or track down [0].
I left a note on the bug r
On 11/04/2011 03:43 PM, Joe Btfsplk wrote:
> A lot of effort is put into helping Tor / TBB users avoid compromising
> anonymity by using Google searches. Yet, the Google search engine is left
> in Aurora. It's a pretty simple question - why?
How should using Google as search engine comprise your
On 11/4/2011 9:54 AM, Christian Siefkes wrote:
On 11/04/2011 03:43 PM, Joe Btfsplk wrote:
A lot of effort is put into helping Tor / TBB users avoid compromising
anonymity by using Google searches. Yet, the Google search engine is left
in Aurora. It's a pretty simple question - why?
How should
On Fri, Nov 4, 2011 at 10:54 AM, Christian Siefkes
wrote:
> How should using Google as search engine comprise your anonymity? Either
> you're anonymous, then you're anonymous on Google too. Or you aren't
> anonymous, then avoiding Google won't help you.
Anonymity is not an either or thing. If it
> We've noticed this issue some months ago with bufferevents enabled,
> but it's not easy to reproduce or track down [0].
Thanks for pointing me to the ticket, I'll try to keep track of it and
help debugging.
Sebastian
___
tor-talk mailing list
tor-t
