Re: Memory usage on relays
Binaries are staticly linked so that someone can't substitute a replacement library. Otherwise you can replace the library or set LDPRELOAD to implement a variety of attacks. On Jan 18, 2010, at 2:28 PM, Nick Mathewson wrote: On Sun, Jan 17, 2010 at 11:29 PM, John Brooks > wrote: [...] As a vaguely related sidenote, is it intentional that openssl is statically linked? I would expect that Tor more than anything would want to benefit from security updates as quickly as possible, and most package managers / people won't rebuild it after an openssl update. Seems a bit dangerous. I was able to confirm that I was running with the right version, though, by adding the following right under Tor's version notice: Tor links against openssl dynamically for me, at least. Let us know if there's some more magic we need to do in src/or/Makefile.am to make it dynamically linke for others. I'm not sure openssl builds shared libraries by default, though: could that be the problem. -- Nick *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/ *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Memory usage on relays
On Sun, Jan 17, 2010 at 11:29 PM, John Brooks wrote: [...] > As a vaguely related sidenote, is it intentional that openssl is > statically linked? I would expect that Tor more than anything would > want to benefit from security updates as quickly as possible, and most > package managers / people won't rebuild it after an openssl update. > Seems a bit dangerous. I was able to confirm that I was running with > the right version, though, by adding the following right under Tor's > version notice: Tor links against openssl dynamically for me, at least. Let us know if there's some more magic we need to do in src/or/Makefile.am to make it dynamically linke for others. I'm not sure openssl builds shared libraries by default, though: could that be the problem. -- Nick *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: QoS and Tor on Ubuntu 9.10
Matias Meier schrieb: > > I’m running tor server on a 100/100mbit dedicated machine which runs > ubuntu 9.10 x86. > > Currently I’m sharing 1mb/s (8mbit/s) with the tor network. But I want > to share more bandwidth with the tor network. > > But on my server are running also other services. Because of this I want > to ask here, if it’s possible that a linux guru can write a little QoS > script for me with “tc filters”. > > I need two different classes for traffic shaping. I don't think you need any nifty QoS features as long as you don't let tor eat up all bandwidth, cpu cycles, sockets, and kernel tcp table space. Just set BandwidthRate parameter in torrc to a reasonable low value. Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Memory usage on relays
John Brooks wrote: > This topic has been addressed before, but then the answer was often to > use/wait for 0.2.1.x or switch to another allocator. "./configure --enable-openbsd-malloc" solved this memory leak issue on my Debian box. Currently tor is using 354m resident memory and 20k open tcp sessions. Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
