- tor-relays - lists.torproject.org

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

Feedback
by torserver＠datakanja.de 26 Feb '16

26 Feb '16

Hello, i have been running a new relay for a short time period now and would like to bring to your attention the issues faced, that finally led me to refrain from keeping this up any longer: * Documentation was ok (on torproject.org) and the installation (using deb on ubuntu) was easy. * It took quite some time to understand the implications (opening ports in the router, hazarding security to my computers, as i was - to this date - relying on the routers firewall working) - This job of mine basically got delayed until later, when i would have learned, what is needed in that respect. * Next, i noticed a frequent (daily) behavior of the Tor server dropping traffic to around zero. Inspecting this, let me to understand, my provider was disconnecting me and reassigning a new IP on a daily basis, which took some time to propagate. Even worse: It did not propagate on its own, i needed to restart the tor service to reinitialise... * Asking in the online channel, i was guided to change my "Nickname" torrc config to match the dyndns entry corresponding to my server. * But this never made it to the directories, thus forcing me to manually restart Tor on a daily basis in order to force the changing IP address into them. * Finally, i was told, this behavior would be disruptive to the network, i therefore brought the service down for good, wasting the bandwith, i was willing to spend, for the near future. :-) * Ok, otherwise, i would have to pay additional fees to rent a server off-site with a permanent IP, but that would be giving more, than what was easily affordable, as my machine is running 24/7 and the connections open anyway. Thus Tor doesnt seem to be able to absorb the kind of bandwith, i was willing to share long time. This is leaving a sad taste on me, who is pretty much interested in privacy, anonymosity, which led me to avoid the mailing lists with a durable email-address. But just using a read-only one wouldnt allow me to post to the list. That is why i created this one temporarily, just to let you know about my experiences... NewTorKidOnTheBlock (this was the name of my Tor relay)

8 10

Re: [tor-relays] Stable Flag Question
by stealth＠nym.mixmin.net 25 Feb '16

25 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 25 Feb 2016 18:41:28 +0100, you wrote: > > > > On 25 Feb 2016, at 18:30, stealth(a)nym.mixmin.net wrote: > > > > Signed PGP part > > I just recently had my Stable Flag removed from my middle relay. It > > appears that my stats have gotten better over the past few days, so > > it's not clear to me why the stable flag was removed. Can someone > > explain how this flag is enabled or not enabled? > > > > Relay Name: stealth > > Fingerprint: A290A9E71ADFC2FB1C80E64EF851A4B905450105 > > Looks like some of the authorities couldn't reach your relay ("Running") last time they checked, and the majority doesn't think it's "Stable" (based on uptime). Perhaps this is because it was restarted recently. > https://consensus-health.torproject.org/consensus-health.html <https://consensus-health.torproject.org/consensus-health.html> > > Perhaps it's because you changed your address or orport on 2016-02-18. > https://onionoo.torproject.org/details?search=A290A9E71ADFC2FB1C80E64EF851A… <https://onionoo.torproject.org/details?search=A290A9E71ADFC2FB1C80E64EF851A…> > (Bug #18050 could cause this, it's fixed in master and 0.2.7, and we're considering it for 0.2.6.) > > Give it time, and enough authorities should believe your relay is stable. > > Perhaps you could consider upgrading it from 0.2.4? > > Tim Tim I have a cronjob that has this command: 0 0 * * * apt-get update -y &> /dev/null && apt-get install tor -y &> /dev/null If there is a new version of Tor and am asking that it be installed. My cronjob is not working, if it's not picking up the latest version of Tor. Can you recommend a change to my cronjob? I just installed this relay about 5 days ago and created the script two nights ago, so I'm not sure what you mean by "Perhaps it's because you changed your address or orport on 2016-02-18". 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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJWz1U5AAoJEH1gNwhiMDZumawQAKeFuwwembr+VsMNH065yhzP +KNbFPzMM9PscX1qv5e3UBhFOI5Rk8vEJkBFxwdEjk2G4sIXD3Y/zNL3+nbTn6VF WcyzlimRNgTBlG4E5t+l3e13aZiLs/9eyUV3LsuchjeGxavno+G0/JKaiWgvrNV9 L6mkVCvRlHj2gcA3h0G4FEV/K+oSSOtD/ZfzL5jVtgS3T2iZuYPb6Z7Mc71bFuUD bgjTmYf6VavbBnqnSdfO8QI0MsNap9M5rBjqlU42J4LwBDW4oMNKjR6F1lkVYdFm 5nGZbMN2dFqSNgxvVIAzTZfNeksnTTmWkm0g3IrHlR3n3GfyC01xOHKap9NAoW6Y dO15zsYcWlYiOWkDCsx067Jn3XqEVtBJl0XERy5WZxFFFDr3Y+LHprN3aySH0bGz EfcIxKwdbpRWygDUnm8Ur22dDl2jVajun5XgQtjesodQjuHQa5oi4kB9m7t7/ThI trqJXwtB1GwQ+OWAR3d8RcjXt8O7ygJwRuk2PXlIfvY3owLOu1j11uDBrV+/HuEP sGKC+tqjEM7wS/rfAose9U7JnjVbb4iUQg3h7f7/ZmkZh1yp76ZixC3yDSAXZJfs wJQGItJcm2xPCHa/ZUhDi0qsDwLND33deJ+ihkqR+FaAn2RjvVbkVAtgZdPF5S+4 vriUnYrcvIRk1Ajx6f9a =r6HX -----END PGP SIGNATURE-----

3 2

Stable Flag Question
by stealth＠nym.mixmin.net 25 Feb '16

25 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just recently had my Stable Flag removed from my middle relay. It appears that my stats have gotten better over the past few days, so it's not clear to me why the stable flag was removed. Can someone explain how this flag is enabled or not enabled? Relay Name: stealth Fingerprint: A290A9E71ADFC2FB1C80E64EF851A4B905450105 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJWzzIwAAoJEH1gNwhiMDZu82oP+wWsR+7M8pOqNtF+lJZ15sGk 7sBPulmb57s1wwBmpbbvCtIalPwRffAOsB3ilwJyohlXAuLWWS6Aeo/s94CHVzE5 V9t2ZUIWvx0nEd8csrGBNJ+AfMDt1KwdJF1gFr+efFhXAbH2ARdQZgKGv6Mye5cf 161OLW+a8hRT3+i9+AeTdYLLz40QSCuWIuspaoPGcORE5LFykhrx63cI/XYnJRJW LsnW3EKitXJw1jib+Bh5afegB2PimzGpA6vMcWRSEiufYkgN+ndfN0lGQyYgji2y /h+FDdYovUGGnt5EBy33Z3Ch4YRYbci95QDzXEMsgxiBesBMZNoz5cbjO7WjOTl/ rh3kfMamMswI+mSZqwU1Wp9xIyBQwJB86KOKdSoaAjA/8nbxiAB8ImY/AOfCyRN3 faQ7SKbV/b3PbAVMXHa1WorJ1wy0xgvru6UTUljE83qZVsmenmgENwn3nz8t3Gqs fRTuDzV3ysEq8o/os41Md914oGFknZRVa7undami9WGmNqtJ0Ck5zPHxOmiQm2nX FSuUUvNvl4hDv+54ZHhD9nPT/LdQY7wQmegJ+I6YM9//Ab2ccZoyGcXzjQMXqkiw 9EPBDen7bSMW2+YJWG0H6emlj0t7VPmkf5jW6/q7YlWV/ak/jwtYa6TqpTRtKgoq /3xpaM9q+XiHFQsS53Me =3iAz -----END PGP SIGNATURE-----

2 1

Re: [tor-relays] Reminder: exit nodes probably shouldn't be using Google's DNS servers
by Tristan 25 Feb '16

25 Feb '16

According to the Tor manual, IPV4 DNS queries are cached by default, but the UseIVP4Cache option says this: NOTE: This option, along UseIPv6Cache and UseDNSCache, can harm your anonymity, and probably won’t help performance as much as you might expect. Use with care! Not sure if it's on by default, or if I should turn it on. On Feb 25, 2016 10:09 AM, "Elrippo" <elrippo(a)elrippoisland.net> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Are you caching the DNS queries? Am 25. Februar 2016 13:47:04 MEZ, schrieb Steve Snyder < swsnyder(a)snydernet.net>: >The OpenNIC servers may not be appropriate for use by a high-speed Tor >exit relay. > >I run an OpenNIC DNS server, and my VPS vendor insisted that I >rate-limit the server to avoid it being used as a DDOS vector. I'm >guessing that this is not an uncommon position to take for public DNS >servers. > >The OpenNIC servers you select for use may be perfectly fine for your >level of use but don't assume it is automatically true. > > >On 02/24/2016 10:49 PM, Tristan wrote: >> They are default for Pulse Servers. >> >> Anyway, thanks elrippo for that link to the Open NIC Project! I've >added >> their DNS servers to my exit relay, and I no longer see any log >errors >> about failing nameservers! >_______________________________________________ >tor-relays mailing list >tor-relays(a)lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays - -- We don't bubble you, we don't spoof you ;) Keep your data encrypted! Log you soon, your Admin elrippo(a)elrippoisland.net Encrypted messages are welcome. 0x84DF1F7E6AE03644 - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.11 (GNU/Linux) mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr 9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN /VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ 6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8 6FNtNKuUkXREybpHwlVAXnHzInmFOOM9RAmF70r3zEmKt77W1ztBLo2o9X79gPgL u9ThgrH6Oc2k46n+9nc3joccr7miiX/bp976DNWcWdOYThiSSOCb8Zw9/Zs935i1 wUVkYTj24tmBH4H5ov9ib7RPmU21ru458RbUKG0ONAqBtAHNyXHzUnXsrke+D4VW MI06YcXSk8YeYgQ8GxgHQc+W2bb8LIbKN1hEYJ0wzM62vKR2/Oiwuf8lXutIKTuz +v7Vj1PQd66DGHsxtWRaWnr1c54JTL2wICHJYKFH4grp7864+GL/uQ1O/Z/XxVku E1JQ/AnwBGU1M1S6otwWGWVRjzEzQtxsfcCEPvV/9td3FIFQAbGTPb+48XFU+TY9 8AlcXBlDzXq7c5f8Evn/oSIsZDt63K4HNTmMGqOTl/p1aA0e4eyX76LczY06rDP5 GMSNs+AHmYgZiS4RYhRUIvS9uLXMnnDAMYst0SDl2orDUUeHBTzu0rchyknBZMGP p5wQuWQ9CFlV+dj3UYbrBwC1lTkAMXRG2vlhA0V0TZqos7A5D4VHgSUQQjE= =otlL - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQJcBAEBCgBGBQJWzyc/PxxlbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0 ZWQpIDxlbHJpcHBvQGVscmlwcG9pc2xhbmQubmV0PgAKCRAkQ93r2VDR61NwEAC2 bVIngcpTcwVBXfZCLmRh0yixDBWOWmA0HLE3U0ow3s2KqPM+QhWr4qtHFcYCTvOR yWBrNXXFD6T5SwKGJdUr9NvBzz4Vw+jCC+pTHdzOaXZJ3cVp0JUudjV+jHykSptO ZAbM60mMTXrT/2fuf6i57j3mMyWiBvPmcqqlcTs+HWLz5pjSXh3FBL+3bYZbNSkf LNqYqE6Z0EpdksyCHR+k3JjtcwZqX6cdDQs+YEQdoeMhxQvadr48WAquwyLTr5RF ybzKLYeUwwknehwvZHJl5GalyYqLWZcEkqRfvH//bqjJH4cYcHEKg+HLFBevurQE tT+BMXx0neTr7HpzeHgrEpBw5REdcEwLBtQMZ5+DlJ+cflz9JiFk9/bc6SqvB1JX phxvysQtVSYoANG19tlT+k9q0uJLXZaS7JSBgtxxyuxhSQnQZHRnEkw6jUeHEWkS Y8+3o+D152L2K3U+NeDxKc2+dZsSY8vbYvIJLfHp48+F50+XbpI7kwQf6c/bGbMt PngJaHEgX4rdas2DyD0SK0gfPBe2X63J7dmE+Rq8X3+9wqx5af0Nk35YuYcGUzkF LInjxW2b3zWAnX2PeyNKxiyHP2Z32h8mAP6CRQLYDtc0HsZzqFGus2y4R+JalQXO 5DOAv36NfZ1qq1mJF5IjUNzHilaC2iYl1fpcqRQd2g== =pcgO -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Reminder: exit nodes probably shouldn't be using Google's DNS servers
by Nick Mathewson 25 Feb '16

25 Feb '16

Hi, all! While looking into a bug report, I noticed that an exit node was using one of Google's well-known public DNS servers for its own DNS server. No disrespect to the operators of Google's fine public DNS service, but my sense is that using it for a Tor exit node might not be the greatest idea for users' privacy, having one DNS provider that gets to see so many requests. It's probably a better idea to have your own local cacheing DNS server. Would anybody like to share a guide about how to set one of those up safely and migrate correctly? best wishes, -- Nick

23 38

CVE-2015-7547 Tor network stats
by nusenu 23 Feb '16

23 Feb '16

Hi, if we assume for simplicity that every relay running Linux that has not rebooted since 2016-02-16 is vulnerable to CVE-2015-7547, than these are the current stats (optimistic, because we assume that everyone that rebooted did also update). Vulnerable relays: +------------+------------------+-----------------+ | cwfraction | guardprobability | exitprobability | +------------+------------------+-----------------+ | 0.586 | 0.639 | 0.518 | +------------+------------------+-----------------+ (1=100%) Apply patches and reboot. Debian https://www.debian.org/security/2016/dsa-3481 RHEL/CentOS https://rhn.redhat.com/errata/RHSA-2016-0176.html Ubuntu http://www.ubuntu.com/usn/usn-2900-1/

9 10

does the Tor network scale well ?
by Toralf Förster 22 Feb '16

22 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Given the numbers of https://torstatus.blutmagie.de/index.php there are about 40 Tor exits which covers 1/3 of the whole bandwidth of all exit relays. I do wonder if under-weighting the big relays in favour of many smaller relays would make it harder for an adversary to de-anonymize the traffic ? Bandwidth (KB/s) percent cumulated IP Address Hostname 0.00% 37188 1.52% 1.52% 197.231.221.211 exit1.ipredator.se 33608 1.38% 2.90% 94.242.246.24 orion.enn.lu 30720 1.26% 4.16% 77.247.181.166 77.247.181.166 30720 1.26% 5.42% 77.247.181.164 rainbowwarrior.torservers.net 30294 1.24% 6.66% 94.242.246.23 destiny.enn.lu 28732 1.18% 7.84% 176.126.252.11 chulak.enn.lu 28721 1.18% 9.02% 185.65.135.227 torproxy02.31173.se 26364 1.08% 10.10% 85.248.227.164 tollana.enn.lu 25927 1.06% 11.16% 176.126.252.12 aurora.enn.lu 22973 0.94% 12.10% 89.234.157.254 marylou.nos-oignons.net 22579 0.93% 13.03% 85.248.227.163 ori.enn.lu 22551 0.92% 13.95% 192.42.116.16 tor-exit.hartvoorinternetvrijheid.nl 21765 0.89% 14.84% 5.79.68.161 Relay-J.tor-exit.network 21280 0.87% 15.72% 93.115.95.204 lh28409.voxility.net 20768 0.85% 16.57% 5.79.68.161 Relay-J.tor-exit.network 20413 0.84% 17.40% 176.61.147.146 176.61.147.146 19993 0.82% 18.22% 65.19.167.130 65.19.167.130 19966 0.82% 19.04% 207.244.70.35 207.244.70.35 19689 0.81% 19.85% 195.154.56.44 tor-exit.gansta93.com 19685 0.81% 20.66% 46.166.170.6 tor-exit-2.netdive.xyz 19662 0.81% 21.46% 171.25.193.132 tor-exit6-readme.dfri.se 19253 0.79% 22.25% 77.247.181.165 politkovskaja.torservers.net 18905 0.77% 23.03% 89.234.157.254 marylou.nos-oignons.net 18319 0.75% 23.78% 93.115.95.206 lh28409.voxility.net 18066 0.74% 24.52% 142.4.213.25 heaven.tor.ninja 18033 0.74% 25.26% 62.210.129.246 relay1.tor.openinternet.io 17932 0.73% 25.99% 188.138.9.49 atlantic480.us.unmetered.com 17904 0.73% 26.72% 65.19.167.132 65.19.167.132 17695 0.73% 27.45% 109.163.234.5 hessel3.torservers.net 17507 0.72% 28.17% 46.165.230.5 tor-exit.dhalgren.org 17171 0.70% 28.87% 194.150.168.95 kaputte.li 16262 0.67% 29.54% 79.172.193.32 toreador.webenlet.hu 14726 0.60% 30.14% 109.163.234.2 hessel0.torservers.net 14637 0.60% 30.74% 85.214.98.239 h2343030.stratoserver.net 14181 0.58% 31.32% 171.25.193.78 tor-exit4-readme.dfri.se 14164 0.58% 31.90% 193.171.202.146 tor2e.ins.tor.net.eu.org 14022 0.57% 32.48% 188.214.129.85 hst-188-214-129-85.balticservers.eu 13987 0.57% 33.05% 171.25.193.131 tor-exit7-readme.dfri.se 13962 0.57% 33.62% 193.90.12.86 tor-1.multisec.no - -- Toralf PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7 -----BEGIN PGP SIGNATURE----- iF4EAREKAAYFAlbLd4QACgkQxOrN3gB26U43/AD+NDFTPFv2XJiq1WetnsYKl7/i P/M5OTj7Vzmmr17GnV4A/3s4/TEVya5OPjXUTl7IRdBRldSuvZ8X06i++TbdSOCK =CxqX -----END PGP SIGNATURE-----

2 1

[WARN]Failing because we have 4063 connections already. Please read doc/TUNING for guidance
by tor-admin＠torland.me 21 Feb '16

21 Feb '16

Hi all, since I upgraded the torland relay from 2.6.7 to 0.2.7.6 I get the following warnings: 09:20:30 [WARN] Failing because we have 4063 connections already. Please read doc/TUNING for guidance. [101144347 similar message(s) suppressed in last 21600 seconds] Google only spits out https://trac.torproject.org/projects/tor/ticket/16929 which does not help me. I don't find the mentioned branch bug16929 in git. Can someone please advise what has to be done to avoid the warning, or point me where I find can the file "doc/TUNING". Thanks torland

4 6

routing script
by Markus Koch 19 Feb '16

19 Feb '16

Hi, after having four entry/middle nodes online I would like to help out with an exit node. Unfortunately you will get in a lot of trouble in Germany for hosting an exit node. I spoke with an VPN provider and they are okay with routing tor traffic over their VPN as long I have exit rulez etc. The only thing I need is a routing script for Debian to route all the Tor traffic over the VPN. Anyone can help me out with this? Markus

5 8

Mexico ISP blocking authority nodes and preventing exit relays.
by Ricardo Malagon Jerez 18 Feb '16

18 Feb '16

I don't know how and why, but since January is impossible to have an exit relay in Telmex ISP. And is harder to reach authority nodes. Someone wrote about this, but is mid February and is the same. Tor 2.8 alpha works pretty good with the authority fallback measures, but I can't implement the exit relay or publish the relay.

3 5

CVE-2015-7547
by starlight.2016q1＠binnacle.cx 17 Feb '16

17 Feb '16

Could someone with a solid understanding of how the Tor daemon interacts with DNS comment on whether and how CVE-2015-7547 (glibc DNS response buffer overflow, remotely exploitable) the bug impacts relay running under Linux?

3 2

Relays with misconfigured MyFamily (declared vs. effective)
by nusenu 17 Feb '16

17 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, the following relays have misconfigured MyFamily settings. 'misconfigured' is defined by declared family does not match effective family (as computed by onionoo's new effectiv_family field [1] - thanks Karsten). Maybe we will see future versions of globe or atlas displaying a diff of the two family sets to make such misconfigurations more visible. Please let me know if you find any errors (I did not fact check the output). +------------------------------------------+----------+ | Contact (truncated) | Fingerpr | +------------------------------------------+----------+ | +1 303-265-9283, rdump@OFTC | 09683D5D | | 0x3AEE83BB539036CA <bb AT symvaro DOT co | 6FDF2D3B | | 0x6F6D60C1 Security Dept <hello@brasshor | 445F1C85 | | 0x6F6D60C1 Security Dept <hello@brasshor | 6BC82EBA | | 0x6F6D60C1 Security Dept <hello@brasshor | 254EB51B | | 0x6F6D60C1 Security Dept <hello@brasshor | B3515F16 | | 0xDE731050 Gareth Llewellyn <gareth@netw | 5CAECF26 | | 0xFD78BCE1 Fruity Oaty Tor Exit <torexit | 1ECD73B9 | | 1024D/1DFBA164 Bernhard M. Wiedemann <to | 172DC95F | | 1024D/39B9820C admin at perfect minus pr | B897826E | | 1024D/39B9820C admin at perfect minus pr | 5FCC8306 | | 1024D/39B9820C admin at perfect minus pr | 2421E10D | | 1024D/39B9820C admin at perfect minus pr | AC7AE98C | | 1024D/39B9820C admin at perfect minus pr | E8B7D19C | | 1024D/39B9820C admin at perfect minus pr | ED9F582E | | 1024D/39B9820C admin at perfect minus pr | B1843B40 | | 1MTUwHFknUyUgRYqpNDYiA2j7sXTYoCe2P | E799227D | | 4096R/8BA2371C Fabian Keil <fk@fabiankei | 34A5FBA4 | | 8192R/0xB431B67770E4AA38 Mikal Villa <me | FE305F8E | | <hneal AT imalazybastard dot com> | CF9E4605 | | <hneal AT imalazybastard dot com> | D12F66D6 | | <periplanetaamericanus AT gmail dot com> | 5B5213C4 | | <periplanetaamericanus AT gmail dot com> | 47D04EC4 | | <periplanetaamericnaus AT gmail dot com> | F19106D7 | | <support at gkware dot com> | E754AA99 | | <support at gkware dot com> | 868A253C | | <support AT gkware dot com> | 48674035 | | <tech AT dana dot io> - 1AgYtavutLAMxUYM | 752DA4A4 | | <tor .AT. jgjtech .DOT. com> BTC: 1QHXLy | 0DA71D95 | | <tor .AT. jgjtech .DOT. com> BTC: 1QHXLy | 31A40828 | | <tor AT 1d4 dot us> - 1N7sBLKvekRD4EUL2b | F1107CB0 | | Abuse Department <abuse AT hartvoorinter | 81B75D53 | | Abuse Department <abuse AT hartvoorinter | 89E3170B | | abuse<__aT>icetor{_DoT===}is - 1GDerBXAJ | 1D9D1C1D | | anders.io | 91361C96 | | anders.io | D56AA4A1 | | anders.io | 3A2192F5 | | Bauruine <torcontact aatt tuxli.ch> - 1C | 63C1904F | | Bauruine <torcontact aatt tuxli.ch> - 1C | 52F7C67B | | BFC62AD3 johannes <tor (@) kontrollappar | 750941D5 | | Big Jim Slade <sysop AT bigjimslade dot | 9AFA555B | | Big Jim Slade <sysop AT bigjimslade dot | ACDC9C49 | | DFRI <tor AT dfri dot se> | A10C4F66 | | DFRI <tor AT dfri dot se> | DD8BD730 | | DFRI <tor AT dfri dot se> | EC84E232 | | DFRI <tor AT dfri dot se> | A478E421 | | Fabian Keil <fk(a)fabiankeil.de> 8BA2371C | 5CE3AD8A | | General Zod <zod(a)kdf.mil> | 556D59FA | | General Zod <zod(a)kdf.mil> | CBABC09D | | GetReal <x50 AT riseup dot net> | 51529D02 | | http://www.onion.network/ <info at onion | F89A5238 | | http://www.privacyfoundation.ch/abuse/ | DC41244B | | http://www.privacyfoundation.ch/abuse/ | 0111BA9B | | http://www.privacyfoundation.ch/abuse/ | DE7DE889 | | http://www.privacyfoundation.ch/abuse/ | 487092BA | | http://www.privacyfoundation.ch/abuse/ | AD86CD1A | | http://www.privacyfoundation.ch/abuse/ | 95DA61AE | | http://www.privacyfoundation.ch/abuse/ | B060482C | | http://www.privacyfoundation.ch/abuse/ | 88487BDD | | https://www.torservers.net/donate.html < | 4E021F36 | | https://www.torservers.net/donate.html < | F657ACB3 | | https://www.torservers.net/donate.html < | 64D500C4 | | iggs <tor.20.iggs AT spamgourmet dot com | 2F557D48 | | jvictors at jessevictors com, PGP 0xC20B | C6DC982A | | jvictors at jessevictors com, PGP 0xC20B | 4B8C39A5 | | jvictors at jessevictors com, PGP 0xC20B | BFA0E9F3 | | jvictors at jessevictors com, PGP 0xC20B | 40DF7E2E | | Kevin <tor AT kberanek dot com> - 14BTbA | 92EA887F | | Kevin <tor AT kberanek dot com> - 14BTbA | A1E02458 | | kingbiskit(a)gmail.com - 18gEJokSQ3uwo3QTM | C921704A | | kingbiskit(a)gmail.com - 1CoXRRwDt6YVTZmJ3 | 3246AF7B | | M.K. Nitrox <mk DOT reg AT t-online DOT | BD912646 | | montanisemperliberi <a> safe-mail.net | E8B6E46B | | Nicholas Merrill <nick AT calyx dot com> | 51BFE90C | | Nicholas Merrill <nick AT calyx dot com> | 0B5E5E70 | | Nicholas Merrill <nick AT calyx dot com> | 84D361B7 | | Nicholas Merrill <nick AT calyx dot com> | E4D1F25D | | Pascal666 at Users dot SourceForge dot N | C9437269 | | Pascal666 at Users dot SourceForge dot N | 5B7AEB14 | | Peter Palfrader | 847B1F85 | | R P <edschlonz AT yahoo dot de> | FF06E7A0 | | Samuel Whited 0x54083AE104EA7AD3 <sam AT | CA54C9F2 | | Sebastian <tor(a)sebastianhahn.net> - 12Nb | EBE718E1 | | snIP3r <sniper(a)restricted-area.de> | 3EE8D536 | | tor TA fejk tod se | 2AFE9201 | | torelay [ANTISPAM at] ruggedinbox [ANTIS | 0559A3D3 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | BAACCB29 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 0B454C7E | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 5A551BF2 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 4436A57F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6D3A3ED5 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 75C4495F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6A29FD8C | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 0C77421C | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 8073670F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | B35C5739 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | E6E18151 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6A37488D | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | E11B6AE1 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 70C55A11 | | Torservers.net <support .AT. torservers | 488239E0 | | Torservers.net <support .AT. torservers | 6B1E0019 | | Torservers.net <support .AT. torservers | C46524E5 | | Torservers.net <support .AT. torservers | 770BE0CD | | Torservers.net <support .AT. torservers | 5C84C359 | | Torservers.net <support .AT. torservers | 20B0038D | | Torservers.net <support .AT. torservers | 5714542D | | Torservers.net <support .AT. torservers | B4F883DB | | Torservers.net <support .AT. torservers | 78213EC8 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 4E918B21 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A494237E | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 35FEEA5F | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 2576BFB0 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A1025D32 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | C8D44E91 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | B7EC0C02 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | FFD6C2CE | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 4C6F66B1 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 43D0AB1B | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A57B43E1 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 9030DCF4 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 3A5F08D0 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 5C1E076A | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 482A381B | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 2D671A4A | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 66CFF345 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 55F5CF9D | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | FEF59210 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | B4A553CB | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 92506510 | +------------------------------------------+----------+ ..based on onionoo.thecthulhu.com's data from 2015-07-15 18:00 [1] https://trac.torproject.org/projects/tor/ticket/16276 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVprfXAAoJEFv7XvVCELh0/FcP/28/dhefuPNQaBNSY59NTZTs snwb9vRlAzhDDm0XmWEMIaawFlNjV8shJD8dWvzSvynWHYQySfrStmDdfkpe5CSC lu9ceE6qhhZe+RkyDPM3PdxLhz29XVK+KvQcDcCeWp6nIHzXIOJL+Xk7v7FoU75S Vx8GjhVQd/aiHJQg96zlpdzkAsU000jG2E3Z2EH+gd4Uypl94wgqd0482LSSehiQ LVbhPt6C8NlX32kZ4yAD3W5cHRoyhg30x076X8XHZ16H6F2l801hhON5X32VmXdv vd/kJ7R9JKo4Uig1Y9hq3qpsRsO8aJaN2JOXMsGw2A+6eNFA2OPFLg3/sNKLgiLV N/CPqDlMVsotMDcXX4iBYSHW0Y+J7vyc5ezxE/rKWzBCBZSnK9Sb5UzcrDnOfJRO ABFv+ZtGxSQYVPcnICVdMr+3Kuk0FnKMm7z2ufYriRxDK573LQgNJQnjZ3Tc3JG+ PIVZun0IN/+1gZmQif57xIjW1OFDbDYbhMtYFYbK9zRd7PidIr5NHcYCkEY4whfP 2vhN4jbtYQZZY/hDAMLZVBKDJ42tOYG/8EaWZeMJ8y/pd+F8EvT7ceWzXwuhYm77 WiK4VsgFU7PR7ETi/DJL+ajmFEjpRJ8QOy3J5E/dq/eumkkzL/eBTPL7ydnTmD/u 9271J4DjQYPfjzVtVqdl =ecVW -----END PGP SIGNATURE-----

2 3

Re: [tor-relays] TOR service wont start with ORPort enabled
by Volker Mink 16 Feb '16

16 Feb '16

Hi ! Nope, that was my first idea. No old TOR process running. Best, volker > On 15 Feb 2016, at 00:10, Volker Mink <volker.mink(a)gmx.de> wrote: > > I think I found something..... > >>> could not bind to 0.0.0.0:9001: address already in use > > Where can i set the binding? Is your old Tor process still running? Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

2 1

Re: [tor-relays] TOR service wont start with ORPort enabled (SuperSluether)
by Volker Mink 15 Feb '16

15 Feb '16

Hi! This command brings no output. So no Port 9001 in use... Message: 3 Date: Sun, 14 Feb 2016 07:48:07 -0600 From: SuperSluether <supersluether(a)gmail.com> To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] TOR service wont start with ORPort enabled Message-ID: <56C08597.10905(a)gmail.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Try running "sudo lsof -i :9001" That should tell you what process is bound to the port, and also give you the PID so you can kill it. ***************************

1 0

Re: [tor-relays] TOR service wont start with ORPort enabled
by Volker Mink 14 Feb '16

14 Feb '16

I think I found something..... >> could not bind to 0.0.0.0:9001: address already in use Where can i set the binding? Feb 14 14:04:59 raspberrypi tor[499]: Starting tor daemon...Feb 14 14:04:59.318 [warn] Could not bind to 0.0.0.0:9001: Address already in use. Is Tor already running? Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.324 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 14 14:04:59 raspberrypi systemd[1]: tor.service: control process exited, code=exited status=1 Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.328 [err] Reading config failed--see warnings above. Feb 14 14:04:59 raspberrypi tor[499]: failed. Feb 14 14:04:59 raspberrypi systemd[1]: Failed to start LSB: Starts The Onion Router daemon processes. Feb 14 14:04:59 raspberrypi systemd[1]: Unit tor.service entered failed state. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Multi-User System. Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Multi-User System. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Graphical Interface. Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Graphical Interface. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes... Feb 14 14:04:59 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes. Feb 14 14:04:59 raspberrypi systemd[1]: Startup finished in 2.206s (kernel) + 22.232s (userspace) = 24.439s. Feb 14 14:05:04 raspberrypi dhcpcd[496]: eth0: no IPv6 Routers available Feb 14 14:05:14 raspberrypi systemd[1]: Time has been changed Feb 14 14:07:15 raspberrypi systemd[1]: Starting LSB: Starts The Onion Router daemon processes... Feb 14 14:07:16 raspberrypi tor[586]: Starting tor daemon...Feb 14 14:07:16.092 [warn] Could not bind to 0.0.0.0:9001: Address already in use. Is Tor already running? Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.098 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 14 14:07:16 raspberrypi systemd[1]: tor.service: control process exited, code=exited status=1 Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.103 [err] Reading config failed--see warnings above. Feb 14 14:07:16 raspberrypi systemd[1]: Failed to start LSB: Starts The Onion Router daemon processes. Feb 14 14:07:16 raspberrypi systemd[1]: Unit tor.service entered failed state. Feb 14 14:07:16 raspberrypi tor[586]: failed. > On 14 Feb 2016, at 23:05, Volker Mink <volker.mink(a)gmx.de> wrote: > > Hey there. > > I recently updated my working TOR Exit from Raspian Wheezy to Jessie and also updatet my TOR-Version. > > Now I got the problem, that the TOR-service wont start when I have the ORPort in the torrc-file enabled. > Port 9001 is forwarded at my router and the Pi is also in the DMZ. Can you please send us the Tor log messages? They usually say why Tor won't start. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

3 2

TOR service wont start with ORPort enabled
by Volker Mink 14 Feb '16

14 Feb '16

Hey there. I recently updated my working TOR Exit from Raspian Wheezy to Jessie and also updatet my TOR-Version. Now I got the problem, that the TOR-service wont start when I have the ORPort in the torrc-file enabled. Port 9001 is forwarded at my router and the Pi is also in the DMZ. ## Required: what port to advertise for incoming Tor connections. ORPort 9001 pi@raspberrypi:~ $ sudo /etc/init.d/tor start [....] Starting tor (via systemctl): tor.serviceJob for tor.service failed. See 'systemctl status tor.service' and 'journalctl -xn' for details. failed! pi@raspberrypi:~ $ pi@raspberrypi:~ $ systemctl status tor.service * tor.service - LSB: Starts The Onion Router daemon processes Loaded: loaded (/etc/init.d/tor) Active: failed (Result: exit-code) since So 2016-02-14 13:03:51 CET; 43s ago Process: 18693 ExecStop=/etc/init.d/tor stop (code=exited, status=0/SUCCESS) Process: 10377 ExecReload=/etc/init.d/tor reload (code=exited, status=0/SUCCESS) Process: 18777 ExecStart=/etc/init.d/tor start (code=exited, status=1/FAILURE) pi@raspberrypi:~ $ ) pi@raspberrypi:~ $ journalctl -xn No journal files were found. pi@raspberrypi:~ $ Any ideas what to do? Best, volker

2 1

relayor 0.1.0-alpha released
by nusenu 13 Feb '16

13 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, relayor is an ansible [1] role for tor relay operators. relayor makes use of tor's "OfflineMasterKey" feature [2] to help protect your ed25519 master keys by not exposing it to the relay at all. Since that requires regular key renewals (default: every 30 days, configurable) this role aims to make this step easy by reducing it to a single command. https://github.com/nusenu/ansible-relayor Main benefits for a tor relay operator ====================================== * security: ed25519 master keys are kept offline * easy key renewal with a single command * security: every tor instance is run with a distinct user * automatically makes use of IPv6 IPs (if available) * automatic MyFamily management * automatic multi-instance setup (configurable) Supported Platforms =================== * FreeBSD * Debian 8 * CentOS 7 * Ubuntu 15.10 * Fedora 23 * OpenBSD (starting with OpenBSD's next release: 5.9) Installation ============ relayor is available via galaxy: ansible-galaxy install nusenu.relayor https://galaxy.ansible.com/nusenu/relayor/ Documentation ============== https://github.com/nusenu/ansible-relayor/blob/master/README.md https://github.com/nusenu/ansible-relayor/wiki playbook examples: https://github.com/nusenu/ansible-relayor/wiki/relayor-playbook-examples migration steps https://github.com/nusenu/ansible-relayor/wiki/Migration-Steps git tags are signed with: pub 4096R/4D705DE9 2016-02-11 Key fingerprint = A7B5 DB91 CE04 C9E0 BE66 446B 8CBE 52BD 4D70 5DE9 uid ansible-relayor signing key (https://github.com/nusenu/ansible-relayor) feedback is appreciated. regards, nusenu [1] https://docs.ansible.com/ansible/intro_getting_started.html [2] https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity/Offli neKeys -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWv3qoAAoJEFv7XvVCELh0H9IP/i7rRh3zrGRiru4uSOjZKUtB Fni5jqCxS29V2GKNIXt075M/osd/ZEcTeBPieHvsfQn1t1Ju4e2HwIt9yjENNycM Hg2VDkJt2wRxIg7hOHihGRqqxY7f85FLOpj4y11EskZMKFosOWJ8DrfBCGxYgLLf vVbPEyS454Kj3ezX5BXQsmMAm97tCWeMLwG1BBLnkA+ift0A+/SHU85vYYLGUdPw htZfxe83+WteziNhm8qOVw0sYlJwU8GAghFGeK/y1oPAUb0SjK9D2UHvldM6YNs8 +9359V2kHLMdqWZawellxxnbMNxjpEoHUlMDLpvmuN/S/MtBOkRGeST8bwVM1kRM NHWn3NfmoKDt1NVBqTHY8RfmG+ODr9AXzyP9q9khNlN+R72r60kPgX8+vGR06g9j 7oFi5t+0SlWK+vExEyl+bLTA74ps3GBpk+w9zM2rhX9hms3pn5AAEDzHANY6YxB7 YCpvd/cpykQFQKo6fvmuk0Igdy91rvVPh21eV2boD8qTQ2eVazNj5NLju+9gpUiW oRBN44v23KBXx+lgGb3FeNbSuzlh63MgQ6W9l7A985mfjyo0Xzw71NT5EjbC0eyM t0rdKY2byjUNOFNzb1emYVeujVIpyZqbyU/9opQGPWo7gDtDm4LwZLLBE/fD01ej F0rvBB9VpGIEp+hrWit+ =+F/t -----END PGP SIGNATURE-----

1 0