Re: Debian/Ubuntu tor users, please check for core files
Hi, no core files on my Ubuntu 8.04 relay. regards, Jan Am 25.11.2010 04:29, schrieb Walt Mankowski: On Wed, Nov 17, 2010 at 03:17:41PM -0500, Roger Dingledine wrote: Hi folks, If you use our debs on Debian or Ubuntu, can you please do ls -la /var/lib/tor/core* as root, and let us know if you have any? No cores on my bridge node. Walt *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Debian/Ubuntu tor users, please check for core files
Jan Weiher wrote: Hi, no core files on my Ubuntu 8.04 relay. regards, Jan Has anybody checked to see whether the Tor instances running on Ubuntu have the ability to leave core files? I've never delved into the details, but I know on older versions of Ubuntu, running ulimit in a shell showed the maximum core file size set to 0. Jim *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Active Attacks - Already in Progress?
On 25.11.2010 08:17, Damian Johnson wrote: The reason the operators of the largest tor relays (Blutmagie, TorServers, and Amunet) operate multiple instance is because this is the best way in practice for utilizing large connections. yep, all four blutmagie nodes are running on a single quad core cpu. The Tor application doesn't scale very well with the number of cores. Thus starting multiple instances on a single piece of hardware is the cheapest option to make use of a gigabit uplink. Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: StrictNodes or StrictExitNodes?
Matthew wrote: I think I am correct to say that StrictExitNodes has been negated in favour of StrictNodes. However, when I use StrictExitNodes 1 I have no problems. When I use StrictNodes 1 and have viable ExitNodes then Vidalia gives the error: Vidalia detected that the Tor software exited unexpectedly. I am using 0.2.1.26 on Ubuntu 10.04. Thanks. This is interesting. I tried it.. and both seem to work for me on my 0.2.2.10-alpha on win2k. But.. when I tried - WarnUnsafeSocks 0 I get.. Nov 25 17:50:03.015 [Warning] Failed to parse/validate config: Unknown option 'WarnUnsafeSocks'. Failing. Nov 25 17:50:03.015 [Error] Reading config failed--see warnings above. Tor then bombs out.. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: StrictNodes or StrictExitNodes?
On Thu, Nov 25, 2010 at 05:52:36PM +, Anon Mus wrote: Matthew wrote: I think I am correct to say that StrictExitNodes has been negated in favour of StrictNodes. However, when I use StrictExitNodes 1 I have no problems. When I use StrictNodes 1 and have viable ExitNodes then Vidalia gives the error: Vidalia detected that the Tor software exited unexpectedly. I am using 0.2.1.26 on Ubuntu 10.04. When Vidalia tells you Tor exited, you should go to Vidalia's message window and learn what Tor said as it exited. In this case I'd guess it's because Tor 0.2.1.26 does not know the 'StrictNodes' config option. It was introduced in Tor 0.2.2.7-alpha. This is interesting. I tried it.. and both seem to work for me on my 0.2.2.10-alpha on win2k. But.. when I tried - WarnUnsafeSocks 0 I get.. Nov 25 17:50:03.015 [Warning] Failed to parse/validate config: Unknown option 'WarnUnsafeSocks'. Failing. Nov 25 17:50:03.015 [Error] Reading config failed--see warnings above. Tor then bombs out.. WarnUnsafeSocks was introduced in Tor 0.2.2.14-alpha. --Roger *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Active Attacks - Already in Progress?
Am 25.11.2010 03:38, schrieb Theodore Bagwell: ** I speak primarily of torserversNet_ numbers 1-5, and PPrivCom___ numbers 004-052. hi there, would you mind to broaden your research covering blutmagie1-4? Its last 24h sustained bandwidth is higher than the cumulated bandwidth of all torserversNet and PPrivCom relays. Currently about 25% of all traffic reported by relays flagged as exit is routed thru blutmagie (50090 KBytes/s of 191341 KBytes/s Tor network's total). This doesn't trouble you? Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Come here! When you want to go shopping,Very cheap
pfont face=TahomaHello/font/p pfont face=TahomaA good web for you :a href=http://www.bestchoosing.info;*amp;www.bestchoosing.info%amp;/a .Hope you will like it./font/p pfont face=TahomaMAC,Tiffany,Nike,Adidas,benefit,GUCCI,Juicy,Chanel etc/font/p pfont face=TahomaClothes,Shoes,Cosmetics,Wallet,Handbag,Sunglasses etc/font/p pfont face=Tahomathey accept paypal,Master Card,Visa Card,quot;Very safe and convenientquot;/font/p pfont face=TahomaAll products with low price and good quality./font/p pfont face=TahomaHave a good day/font/p *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Active Attacks - Already in Progress?
Hi, would it be noticed if an adversary modifies Tor's source code in order to report a fake observed bandwidth (a few KB), fake uptime data, and Windows as OS to the directories? Probably nobody will notice even if those relays carry a significant amount of traffic. Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Tor 0.2.2.19-alpha is out
Yet another OpenSSL security patch broke its compatibility with Tor: Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b. https://www.torproject.org/download/download Changes in version 0.2.2.19-alpha - 2010-11-21 o Major bugfixes: - Resolve an incompatibility with openssl 0.9.8p and openssl 1.0.0b: No longer set the tlsext_host_name extension on server SSL objects; but continue to set it on client SSL objects. Our goal in setting it was to imitate a browser, not a vhosting server. Fixes bug 2204; bugfix on 0.2.1.1-alpha. o Minor bugfixes: - Try harder not to exceed the maximum length of 50 KB when writing statistics to extra-info descriptors. This bug was triggered by very fast relays reporting exit-port, entry, and dirreq statistics. Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183. - Publish a router descriptor even if generating an extra-info descriptor fails. Previously we would not publish a router descriptor without an extra-info descriptor; this can cause fast exit relays collecting exit-port statistics to drop from the consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195. signature.asc Description: Digital signature
