Re: [tor-talk] Tor hidden services not working

2014-04-13 Thread sssheep
On Thu, 10 Apr 2014 20:02:43 + (UTC) Cyrus cyrus_the_gr...@riseup.net wrote: Apr 11 19:58:42.000 [notice] Your Guard v235 ($F3416AAAC641B106022BC051F64DBBA18C52D8CF) is failing mor e circuits than usual. Apr 11 19:58:43.000 [notice] Your Guard relaynet

Re: [tor-talk] Does Tor need to be recompiled *after* the opensslupdate?

2014-04-13 Thread Geoff Down
Apropo this, Tor has a helpful message when restarting after updating Openssl via Macports: [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 107f: OpenSSL 1.0.0g 18 Jan 2012; running with 1000107f:

[tor-talk] browser fingerprinting

2014-04-13 Thread Randolph
http://arstechnica.com/tech-policy/2010/01/even-without-cookies-a-browser-leaves-a-trail-of-crumbs/ https://panopticlick.eff.org/self-defense.php Anonymity is quite easily broken, if cookies cannot managed (e.g. like in certain browsers) and if javascript is enabled. As far as we see, Firefox in

[tor-talk] Heartbleed bug / Mainstream information

2014-04-13 Thread Christopher J. Walters
The discussion on the Heatbleed bug has apparently stopped here, and just about everywhere else, but I found (courtesy of another mailing list), some more reports on it, that you may have not seen. These reports suggest the the NSA knew about and exploited the bug for at least two years, and

Re: [tor-talk] Does Tor need to be recompiled *after* the opensslupdate?

2014-04-13 Thread Geoff Down
On Sun, Apr 13, 2014, at 07:29 PM, Geoff Down wrote: Apropo this, Tor has a helpful message when restarting after updating Openssl via Macports: [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with

Re: [tor-talk] Heartbleed bug / Mainstream information

2014-04-13 Thread Артур Истомин
On Sun, Apr 13, 2014 at 04:01:09PM -0400, Christopher J. Walters wrote: The discussion on the Heatbleed bug has apparently stopped here, and just about everywhere else, but I found (courtesy of another mailing list), some more reports on it, that you may have not seen. These reports suggest