tor-relays February 2016

tor-relays@lists.torproject.org

62 participants
48 discussions

Any known Tor relay seizures (in Germany)?
by Thomas 29 Feb '16

29 Feb '16

Hello everybody, do you know of any relay seizures of non-exit relays? In the legal FAQ [1] this "risk" is only listed below exit relays. Have there been any of such events in Germany (either exit- or any other nodes)? Would I have to worry about seizures if I run a guard or middle relay in Germany? Regards, Thomas [1] https://www.torproject.org/eff/tor-legal-faq.html.en

4 3

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 43
by stealth＠nym.mixmin.net 29 Feb '16

29 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 28 Feb 2016 20:21:45 +0000, you wrote: > > > On 28 Feb 2016, at 21:17, stealth(a)nym.mixmin.net wrote: > > > > > Is your OpenSSL compiled optimised for your processor and for the encryption that Tor uses? > > > > > > > I am using the OpenSSL that was compiled for my version of > > Mixmaster as I am running a middle remailer on the same VPS. It is > > OpenSSL: 1.0.1e > > Does Tor log a message when it starts recommending an optimised version of OpenSSL? > There are no references in my notices.log and my .log file is empty. I will temporarily change my log level to debug and see what it shows. > > > How much RAM does your VPS have? > > 512KB > > This is likely to be your issue. 512 MB is not enough for a large relay. > Tor will limit its memory and connections to stay under about 3/4 of the memory you have. > Try 1GB. > > Tim Thanks for advice. Unfortunately upgrading to 1gb is not an option for me. Right now it appears that Tor is not using anywhere near what is available in memory as evidenced by my top command. top - 12:49:36 up 5 days, 20:32, 2 users, load average: 0.05, 0.09, 0.08 Tasks: 70 total, 1 running, 69 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.3 us, 0.5 sy, 0.0 ni, 98.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 524288 total, 198400 used, 325888 free, 0 buffers KiB Swap: 524288 total, 0 used, 524288 free, 37620 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2535 debian-t 20 0 99116 69m 2980 S 3.3 13.5 125:37.86 tor 2422 root 20 0 131m 5108 1080 S 0.3 1.0 5:04.66 fail2ban-server 16014 debian-t 20 0 107m 22m 2516 S 0.3 4.5 6:21.65 arm > > Tim Wilson-Brown (teor) > No response necessary. Thanks for your feedback Tim. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW01+NAAoJEH1gNwhiMDZuctQQAKtZM7sQpue4+SpW+o0hdvpO I6XLk9YWHTszJehj5Gk3ik01yBdBiOgD2SJ2rx/cjR4AnRkRyjN6LOt3g/KxnTYI 4FNGo4fygYn4Oeu+HXmtEey3wyCVxWAzsmCXGNO6LhZhupfdmlv/ftcvcGI9VrJQ wNZTW7QeHpUCJLBt9fbh7Drw+MNwLycwHdmV5kvCWWGK1vqzpWOK44Wmk4lz5+lv ung5/HRHpt865SkXp0l/+w+p4qgTSgZ3thXpqtH1mHQPt52n4PKdUDF3Mf1yXYuf JdOTBNThzZ4s4KNj3cdWH4Wf3wPwpIZ5zCZQ2O+osMpTeOSTOZHwPmStNFdM/CuH OtLxJQb5TaVoUjOqzfcetMbx/5JlT1cutDOL5fVCiGSJ7j6q+FekknkrtKxtIKdU gUobGBJ1u8Ei7axaR7rwcL3egouugQYfDHEEFZdYBBW0tgeNx8l6SCEt7IfqEqhW Fmy58WUBs27ei9dnl9I/xq2V9FYBjdN4tpis22wctife/hth8hJWsMTLJYqP7qj9 9jqcJCgs7b7tkQsem72ApWMAgYnXVCMYscnPKTWdCEw9rdiarmArgPfE0AYuo6Lq NIVg4IADmc/X4Y1SUKq/bYW5vkfIhHKA4aoZUZRj2AL6dcLtj5clAL9MnmyKDB7a 1Ie9DF8NEKkTldYHh5IN =o3VV -----END PGP SIGNATURE-----

1 0

Tor Process Being Killed on VPS
by Stephen R Guglielmo 28 Feb '16

28 Feb '16

Hello, I have a VPS with 512 MB RAM. I run nothing on it except nginx and a Tor relay. The relay is an entry guard and moves about 20 MB/s. It seems that the kernel is killing the Tor process with "out of memory" errors. Are there any tips for mitigating this? I don't have the money right now to upgrade to the next higher VPS plan which has more RAM, unfortunately. Maybe there's some config settings that I can modify to limit the RAM usage? Or, am I just out of luck? Thanks, Steve

10 12

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 41
by stealth＠nym.mixmin.net 28 Feb '16

28 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 28 Feb 2016 13:49:20 +0000, you wrote: > > > Message: 2 > Date: Sun, 28 Feb 2016 12:02:13 +0100 > From: Tim Wilson-Brown - teor <teor2345(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Network Bandwidth Fine Tuning > Message-ID: <A09CFFB4-5ACA-44B4-B813-7DC0B30A4C06(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > > > On 28 Feb 2016, at 02:14, stealth(a)nym.mixmin.net wrote: > > > > What processor is on your VPS? Here is my lscpu output: root$ lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 Vendor ID: GenuineIntel CPU family: 6 Model: 58 Stepping: 9 CPU MHz: 3300.152 BogoMIPS: 6600.30 Virtualization: VT-x > How fast is it? See above > Does it have AES-NI? I believe so. Here's the output from: grep -o aes /proc/cpuinfo aes aes and here's the output from: grep -ml -o aes /proc/cpuinfo aes > Is your OpenSSL compiled optimised for your processor and for the encryption that Tor uses? > I am using the OpenSSL that was compiled for my version of Mixmaster as I am running a middle remailer on the same VPS. It is OpenSSL: 1.0.1e > How much RAM does your VPS have? 512KB > > Have you read the torservers.net Tor tuning advice? Yes I have made several modifications to my RelayBandwidthRate and RelayBandwidthBurst. I have also modified my AccountingMax number. Here's the pertinent information from my torrc file: RelayBandwidthRate 50 MB # Throttle traffic to 100KB/s (800Kbps) RelayBandwidthBurst 80 MB # But allow bursts up to 200KB/s (1600Kbps) AccountingMax 100 GB > (And similar articles?) Any additional links would be welcomed. > > Tim > > Tim Wilson-Brown (teor) > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW00AMAAoJEH1gNwhiMDZu2wYQAImPETHwRvlxrlAclulMlB+n WwPB/fMSjiVwA9Rllb7w8NvSbf2Tu9FmeGoYOUDYTWuq93RsUuQFtVvcw3MXkzBR X/TXAdP9WSDlNiOZajaRNR1hcYQJ0gJqJ9/6oyC1XoDNTK7bcE3FOY5ui10M+fFL rXgM/qBmu+toaqA2vL4DKp3eFYMYDgVmesQLEI6edUvHjK4+itdV9pRwXAvQaFjJ M7We374Siw6izM6cJqXtW3XytUCfIbVyzL+Al93fEJnJDaO5V3kIlHDkjcWJn9ev Ogvg1/zZouwfFFJfC1p29NTsEzy8aF+w3obtq6NWQ0/pzTXJ/sPYIE21EHRIuMJo J2Rk9YPVwp5ckIKH48Eg6jdGjNCI6rs59hhNJfvismvJES+NjgLoqJ+Y59ZnhMjr q4rUssRxyzDFqDdBM60llXfTOh0qEFeHDkeBMfR+F4TJH8SZeEBXW3kyFnG6TH6R D/BoV9ItHi7qXiP9zDIMHTSCz7NNJ210uVdHbMUkMH1He+5bB/auCNRcjXmPwbYg kwbzJlgumSSd4kKufEnvC9KQComniYph90yDr8pOBnCE5E/o8+yVfB7XmTLidNEG Ii/xhSKpdt+E7wQX3ISR2pbJ73tk+FaSd2iPVK0jPWab/zoGqVzZr41VFAWi8n6S tuuLxJ5Lum3gu7EH6M0X =h78g -----END PGP SIGNATURE-----

2 1

Hidden Service on several relays + same .onion
by Pierre L. 27 Feb '16

27 Feb '16

Hey all, Thinking about having fun with hidden-service webhosting on few relays. If I'm not wrong : Host DNS name .onion of a server is stored in the file /var/lib/tor/hidden_service/hostname, there's another file private_key... So my idea is to host the same website on 2 relays with different WAN IP, fingerprint, etc....... But if I copy those 2 files "hostname" + "private_key" on 2 or 3....... relays, will it be ok ? With this set up, if 1 relay is down, the 2nd can be reachable with the same .onion DNS name ? Will this failover method work, or will be it a mess with 2-3 relays with the same .onion name ? Do someone have tried this ? Thx all!

2 2

Notices.Log Message
by stealth＠nym.mixmin.net 27 Feb '16

27 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can someone explain the message below regarding bw_accounting and the lack of a master identity key in my notices.log file? [warn] Failed to unlink /var/lib/tor/bw_accounting: No such file or directory Feb 26 10:04:02.000 [notice] It looks like I need to generate and sign a new medium-term signing key, because I don't have one. To do that, I need to load (or create) the permanent master identity key. Feb 26 10:04:02.000 [notice] Your Tor server's identity key fingerprint is 'stealth A290A9E71ADFC2FB1C80E64EF851A4B905450105' Tor Version 0.2.7.6 (Installed today) Debian 7.0 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW0N8pAAoJEH1gNwhiMDZuSl0QAKeE6APr57XI44RJxKEV/zLC 75DQRZCqdsQh5ReQ+qODFvZ/t+on+/XTFBm7gX0Lit2ylEQEyvmUQpXRWwl4pEH0 ZZh2EGND1phHqn7v2wmlWruEWor+ittYyYp4o2a8RIj4Ed07XEnIcTfTX0WzXXBE khj/FPDnzG60CceYld1ZLFhBuYLCl3gjG0RY9HJFh+rXfsrlrvSSuEYOzOgWdlCW +Ethj62CKEXAkaJDMziR0pLXHbkH5rUqIaI0v8F0C6BrrNzwvydWgnaQjZ0z2OpW CW2O6BCgLsLqmHZThl9QAuqGSPN9v4hTez8fR0S58lvf2865jwrsaK3lWm2JSuOU rUxeS46z9qdJdKu/EuB0TbtNU5A+eYIzUuI9Rn6KkslndxywvnVVLLa0yilM8VOR aHIDSa7UzVDFmqqs1um+xeCWZU1y/f2z2WHyBcNO8/TYZ46z6R5pQ/egpPkiROhc ZvduYSeXaWjhUW1xWHZS8At7/P5+MGkfMXj10RWY4Qj2KvQprxgDqj2ar8n4/XCm 61l74W4ybDdyntm+8uNcXFufiRVmHJYf0YtJnXR/a44LR/XyiCh/DWBOlp3dqH8/ arVvpmKae6CDnG+Rk1giu48Uj8CaP60vq6pzO8wbpezB/P3r/KN15g4P3u+5XmfV ye92npDkwAyshyjAJJue =ngF/ -----END PGP SIGNATURE-----

2 1

Nyx Project Ideas
by Damian Johnson 27 Feb '16

27 Feb '16

Hi wonderful relay operators. It's GSoC season again, where students can be funded to make open source projects like Tor even better! Nyx (previously known as arm [1]) has been my main focus this last year and is inching ever closer to release. For those unfamiliar with it, Nyx is an ncurses monitor for Tor relays providing a bandwidth graph, event log, connections, config editor, and more. Rather than add new features my work has focused on making Nyx simpler and faster, but GSoC provides us an opportunity to do even more. So I'm curious - what do you want from an ncurses monitor? The answer may be 'keep it simple'. Feature creep does us no favors. But if there's a good fit I'd love to mentor a project that makes your lives even better! I'm not overly fond of the ideas I've had so far... * Windows support. This poses a few challenges. [2] * When running multiple tor instances on a single system connect to them all, aggregating the information. So anything come to mind? Cheers! -Damian [1] https://www.atagar.com/arm/ [2] https://trac.torproject.org/projects/tor/wiki/doc/arm#Windows

3 3

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 30
by stealth＠nym.mixmin.net 26 Feb '16

26 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 27 Feb 2016 00:20:38 +0500, you wrote: > > --Sig_/PllBt_/1sHfmWgs/aS1Ks.r > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > On Fri, 26 Feb 2016 18:24:57 +0000 (GMT) > stealth(a)nym.mixmin.net wrote: > > > > [1] https://packages.debian.org/wheezy/tor > > > [2] https://www.torproject.org/docs/debian.html.en > > > > > Thanks for the links above. I have updated to 0.2.7.6. I had a > > hickup initially trying to launch arm as user debian-t. I had to > > kickstart it with just arm and then I killed the program and > > launched it again as user debian-t and it launched. > > The username is debian-tor. Not sure where you're getting "debian-t" from, = > if > from "top", then it might be simply cut off there. > > --=20 > With respect, > Roman > Yes you're right about the debian-tor user name. I was in a hurry when I typed the last post. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW0L/sAAoJEH1gNwhiMDZue1cP/R0Z8Cyn2nERoYWB6qngccoq 6cpAIgdunSLJeT8VvvL6iTwXiIPpy9GqrrloGegHuRrWgPkiood1EmhvNi9cajWQ RRitQVmhCZ9MV7qzMOyGXFZ+J97TgviKeWG+jVJbRSOvqiY88im5InlJhR7smc2f OUaYpwMpm7l6+chSewmy7hRVHLb7jfvWgej8eJc8EJsDAmwnozNrjStqpndRinCn 9gkqzkZEiug1uXJXRS4ZQa3rk087Q9SQkjdYvlI4XfjiQKDKWVMkddDMRpYbo8iR RrKTd01m2i8M2xiG4vDPI+U4T3oOr/6F8XTyvyaz2oziXZDVuRTg9JbDS0a0/wQ8 duiKUpDSNwwrW7+ruS0oJcFD45s5P1GVed9rhDpkDq1KKMF+oNmy/K/vo3uPOLtI lRtVXFq0gsBviZQ3ad+C6epTgMPpF3Yf3Lkpf8vW2jHdypzv3zNZGXfnzzvMVq6d CEGf+/+5C/3N3ZPw4f03tEU2uUzIOCc0E5xYrPktUwRYxn8QNTd39Oc92/deErzH 3kMxY9n42/YEeI0NG/0W8MO1hOQAk1OffbsGfvuZLItPi7LXZY68wEhm6oGDdzI8 alHqXoFHOIMDlnMFNEEpsPg3f5VhE2UtsYUu6JOBHUEQAVHPHavKIPa6UqdCvy8n ER8eCLuvRGpfpe8Hbudt =eEZc -----END PGP SIGNATURE-----

1 0

Light Bandwidth Monitor (like Munin)
by Pierre L. 26 Feb '16

26 Feb '16

Hey all, May be RPi users... and others linux users! I'm looking for a light bandwidth graph software producing html files, to monitor and graph up/down eth0 bandwidth used on my RPi Tor relay. Something like "munin" or "cacti", but I remember this one was very heavy on a RPi v1... It was taking tooo much time to collect/treat/graph :s Which one are you using on your RPi's ? Thx all for your answers !

5 5

Re: [tor-relays] tor-relays Digest, Vol 61, Issue 30
by stealth＠nym.mixmin.net 26 Feb '16

26 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 26 Feb 2016 04:39:26 +0000, you wrote: <snip> > > Message: 3 > Date: Thu, 25 Feb 2016 22:27:36 +0100 > From: Tomasz Nitecki <tnnn(a)tnnn.pl> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Stable Flag Question > Message-ID: <56CF71C8.6000007(a)tnnn.pl> > Content-Type: text/plain; charset="utf-8" > > Hey, > > On 25/02/16 20:41, stealth(a)nym.mixmin.net wrote: > > I'll monitor things and see if anything changes, but I'm more > > concerned that my cronjob is not working. I also did a "service tor > > reload" to see, if anything changed and I still show 0.2.4.27 as my > > Tor version via the arm program. > > Aren't you running an older release of Debian (wheezy)? You can check it > by running 'cat /etc/os-release'. Your tor version seems to be equal to > the one available in wheezy repository [1]. > > In order to get a more recent version of tor, you should add torproject > repositories (wheezy version) to your apt sources. Comprehensive > tutorial, on how to do that, can be found at [2]. > > Anyway, you might also consider upgrading to the latest Debian release > (jessie). > > > Regards, > T. > > [1] https://packages.debian.org/wheezy/tor > [2] https://www.torproject.org/docs/debian.html.en > Thanks for the links above. I have updated to 0.2.7.6. I had a hickup initially trying to launch arm as user debian-t. I had to kickstart it with just arm and then I killed the program and launched it again as user debian-t and it launched. Not sure what the issue was there. Now I hope my cronjob works at the next update. Time will tell. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW0JWxAAoJEH1gNwhiMDZuiRIP/13REHWzwvvtfqOa/8czNQSz FP6aPCrCQaAraGp3dYEWIdKgdHMC6k4icdDWR8zKCdAkVMpfSTWnivLF/ZuY9l4u qQplHRONI+r7s6nng2iYcFGCTl/+tCBZxHbjCrv6GPRQLcVCyWOg5/PhUqZOTEaq cfI9hHjscArnwbVRE9DWfZbj+zTlDENM6pvngtqHPTl5V84gcxcZysddOXyqz6Q6 UKRX6tAUvj7/vdLDyEinBLb9o4SLgsEfkANm/OTsOD6+33Zv7iWdxf5k1sMDuYcv FtKSoL2ZbN2VMmDGdKA895uN4gkiUhWJ5fCktBDnAbeJUN+DOHUU8muuN4DgxjH0 YhTHy/+44l1aMQU9oWBdoJrhIvnAz0aYni0iy9URGPDoTZb92zOVlIJyKayGKLwy TOAZyKB3fI6tcRn1+H5QljitX2kxMCwEO7PU9WaWadPcMnqmhNB+9dFBLyxPSM0S BhgfPHVT/HNDBDdLc9xrvJr9XvNJ/Q5D1O9NLnKKpF5iEHyFq9pGsvan3TRYcnA1 tsmJkLSCSOeV/t9xUaSg/Unhp34TqoTO2e0lKl3D4Fa8toBSS2h7MXM/Rv74hdK9 9po7Ez8YcirfWv34voKofZkN503lrxt2lz+bxzFiCDcofWIVOEMWf3AG0O8mCVi8 pqvMbCIOfOkk2htEVLZz =XzOu -----END PGP SIGNATURE-----

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays February 2016