- tor-relays - lists.torproject.org

tor-instance-create users: beware all your instances are always started
by tor relay 06 Aug '16

06 Aug '16

This is only relevant for debian users. If you assume you can manage your instances with the usual systemctl commands like systemctl disable/enable tor@myinstance beware that they have no effect. Note: systemctl start/stop works as expected. This is important to know especially if you have multiple configurations and want to enable/disable some of them to avoid running them concurrently. I don't know the reasoning behind that design decision but all your instances are enabled due to [1], you cannot use the well known systemctl disable command like systemctl disable tor@myinstance to disable a specific instance. If you want to disable them you can use the 'mask' command: systemctl mask tor@myinstance this is less convenient because this way you wont be able to run systemctl start tor@myinstance (on a masked unit) or move configuration files away (also less convenient than native disable/enable) [1] https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor-genera…

1 0

debian: log messages when upgrading tor package
by tor relay 05 Aug '16

05 Aug '16

When upgrading the tor package on debian I get the following syslog messages: systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument systemd[1]: Failed to reset devices.list on /system.slice/system-tor.slice: Invalid argument Should I be concerned?

1 0

Got a visit from the police this morning..
by Stig Atle Steffensen 05 Aug '16

05 Aug '16

I never thought I would be one of those operators who had to deal with the police or anything like that. I've done all I can to set things up so that it's easy to see that I run a exit node. I have a disclaimer on my website : https://stigatle.no/index.php/tor-exit-node/ and if you go to the ip of the node, you'll see the same info: https://185.97.32.18/ I run this node - which is no secret: https://atlas.torproject.org/#details/04250C3835019B26AA6764E85D836088BE441… So, back to earlier this morning. Suddenly got a hard knock on my door, I was surprised because we never get visitors. I saw it was the police (2 officers), and they asked if we could talk in private, because they heard my kids (2 and 4) and my wife upstairs, I said yes, no problem, let them in. They would not let me know what it was about at first, they asked a lot about what I did yesterday, easy for me to answer since I was out climbing mountains all day long. Then asked a lot about who has access to my connection at home, It's just me, my wife, no one else. Then I start to ask a bit, and I thought about the exit node I run, I quickly confirmed that it was the exit node (which is in sweden and not in Norway where I live) that was the reason why they where at my house. All though - 2 second check would confirm to them that the server is not at my house, and the impression they gave me until I showed the Exit node was that they thought it was sent from my house. I have blocked the email ports on the exit node, but the issue was that a email had been sent through hotmail (web), threatening Angela Merkel, that's why they where at my house this morning. I got the chance to explain everything as best I could, explained how it all worked, and why I run a exit node, and I feel they got all the answers they needed. They then left - and for now that was that. I would be put on some kind of list, but that list would also explain that I operate a tor exit node. I'm happy with that, and hopefully this will be all that there's to it. I might have to do some more explaining if I travel to sweden\germany, but that's fine with me. Anyone else here that has this happen to you recently as well?..

11 13

Syslog: Kernel TCP: Too many orphaned sockets
by Tristan 05 Aug '16

05 Aug '16

I looked at my exit relay's syslog for no specific reason, and saw that it was flooded with the following message: kernel: [1736405.162223] TCP: too many orphaned sockets These messages occur multiple times per second, but they only flood the log every couple of hours. What is this, and what does it mean? -- Finding information, passing it along. ～SuperSluether

3 4

Any security tips on running a TOR relay?
by Andrew 05 Aug '16

05 Aug '16

Hi, I've got a spare server for two (freebsd) and I'd like to start running TOR relays on them. Is there any security concerns I need to deal with, or is the ports compile + updates good enough to keep my systems decently secure. I actively monitor the machines, but as you know, the game is prevention, not reaction to security incedents :) Thanks, AB49K

5 11

Two bridge relay questions
by Tor-Node.net 05 Aug '16

05 Aug '16

Hi! I run an obfs4 bridge. 1) Why is the advertised bandwidth 56.72 KB/s when the relay is on a (shared) gigabit connection? According to my experiments it should be several MB/s. 2) Where can I submit my bridges to help people in Iran, China etc, besides the Tor BridgeDB? Kind regards Tor-node.net

3 2

Exit relay funding
by Michael McConville 04 Aug '16

04 Aug '16

Hi, everyone. I'm an experienced Tor relay operator and a mostly dormant community member. My main relay these days is on a dedicated server running OpenBSD and moving 3-4 MB/s. It costs me $35/month. https://atlas.torproject.org/#details/CDAB3AE06A8C9C6BF817B3B0F1877A4B91465… Sadly, I have to shut it down at least temporarily if no one can help me pay for it. Is anyone interested? You can search the mailing lists to see that I've been contributing for a few years, and I can give more verification if you'd like. Thanks for your time, Michael McConville

23 40

Re: [tor-relays] tor-relays Digest, Vol 67, Issue 11
by Flipchan 04 Aug '16

04 Aug '16

Auto update with cron, audit it like a normal server tor-relays-request(a)lists.torproject.org skrev: (4 augusti 2016 14:00:07 CEST) >Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > >You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of tor-relays digest..." > > >Today's Topics: > > 1. Re: experiences with debian tor 0.2.8.6 package from > deb.torproject.org (tor relay) > 2. Any security tips on running a TOR relay? (Andrew) > 3. Re: Exit relay funding (Petrusko) > 4. Re: experiences with debian tor 0.2.8.6 package from > deb.torproject.org (Peter Palfrader) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 4 Aug 2016 08:01:32 +0200 (CEST) >From: tor relay <torrelay3(a)mailbox.org> >To: tor-relays(a)lists.torproject.org >Subject: Re: [tor-relays] experiences with debian tor 0.2.8.6 package > from deb.torproject.org >Message-ID: <249633305.6901.1470290492290(a)office.mailbox.org> >Content-Type: text/plain; charset="utf-8" > >https://trac.torproject.org/projects/tor/ticket/19825 >

1 0

Tor relay on pfSense
by Edwin Garzón 04 Aug '16

04 Aug '16

Hello you have an updated tutorial for "Set Up Tor relay on pfSense 2.3.2" Thanks Edwin

1 0

Re: [tor-relays] is explicit DirPort needed anymore under Tor 0.2.8.6?
by Tristan 03 Aug '16

03 Aug '16

I'd like to peep in here and say that Orbot (Tor on Android) is still using version 2.7.5. Until someone updates the app to 2.8.6, those users will still need a DirPort.

1 0