- tor-relays - lists.torproject.org

'No space left on device' glitch causing log failure
by Geoff Down 10 Oct '16

10 Oct '16

Hi all, these are the last entries in my log, but my bridge is still listed on Atlas and client functionality is fine. Latest stable version on OSX10.4. Needless to say, the disk is not full and 'tor' can write to that directory just fine now. Oct 05 22:52:09.000 [warn] Couldn't open "/Users/tor/tor/state.tmp" (/Users/tor/tor/state) for writing: No space left on device Oct 05 22:52:09.000 [warn] Unable to write state to file "/Users/tor/tor/state"; will try again later Oct 05 23:10:27.000 [warn] Couldn't open "/Users/tor/tor/cached-consensus.tmp" (/Users/tor/tor/cached-consensus) for writing: No space left on device Oct 05 23:11:32.000 [warn] Error writing to "/Users/tor/tor/cached-descriptors.new": No space left on device Oct 05 23:11:32.000 [warn] Unable to store router descriptor {more of the same until Oct 05 23:11:34.000} GD -- http://www.fastmail.com - Access all of your messages and folders wherever you are

4 4

tor relay and syslog logging
by Dr. Who 09 Oct '16

09 Oct '16

I'm trying to log locally (notice.log) and to a local syslog-ng server. It doesn't seem to work. I get no messages at all to my local syslog server. When I try to log some testlines manually (even as the tor system user) it seems to work. As I understood the configuration I can have multiple "Log " lines without problem, right? A test like: logger -p daemon.notice -t tortest Testing generates the expected lines in /var/log/messages What facility is used by tor when logging to syslog? I didn't find that information. System is a standard current debian 8.6 with tor Tor 0.2.8.8 (git-8d8a099454d994bd), the two Log-Lines are: Log notice file /var/log/tor/notices.log Log notice syslog Any idea what might be missing?

2 1

ISP, Abuses , Intrusion Prevention etc.
by pa011 09 Oct '16

09 Oct '16

My personal efforts over the last months as well as the recent discussion about Intrusion prevention showed, there are more and more ISP's not giving support any more for running Tor exits, either in not allowing new ones or even shutting down existing ones. Sure there are still chances to find new inexperienced ISP's, which in the willing to increase their customer base give allowance to run an Exit. But only a few weeks later their wish to get rid of you again increases with the same speed as the stack of abuses rises.Finally you are out again and on the back of their terms not even able to get your unused money back. Further doing it that way, is kind of leaving scorched earth behind you and not only yourself, but for Tor as a whole. So there are at least two questions: - what forces drive ISP's to behave like they do with abuses? - maybe Exit volunteers and here especially the big ones could ask some questions to their ISP to get more light on this I do refer to my old questions -still unanswered: -is it just the more work for rather poor money handling(forwarding) those abuses ? - to whom else do ISP's have to report what they are doing with received abuses? - must ISP's answer to the origin of the abuse? - who is getting a copy of all that conversation(if at all)? - can an ISP loose its license (with too many or badly handled abuses)? - are there any regulatory burdens for them - if so which ones? - are ISP's treated different in different parts of the world? - could there in the medium therm changes be made the way Tor operates to bring down the non linear increase of abuses Support terribly needed and appreciated! Paul

1 0

Intrusion Prevention System Software - Snort or Suricata
by pa011 09 Oct '16

09 Oct '16

One of my main ISP is going mad with the number of abuses he gets from my Exits (currently most on port 80). He asks me to install "Intrusion Prevention System Software" or shutting down the servers. He personally recommends Snort or Suricata. As far as I understand implementing such a software is not going together with Tor - am I right? Somebody having same or any experience? Thanks Paul

15 96

Relay uptime after restarting Tor service
by Zac 08 Oct '16

08 Oct '16

Hi, I run this relay: https://atlas.torproject.org/#details/02928855BFAD787F8B363F21860D1E7D156E0… and noticed that my uptime on Atlas is reset to zero when I need to restart the service, i.e. for updates or configuration changes. Is this expected behaviour, or should the uptime in fact be unaffected by such short down-times? Thanks, -- MrDetonia <mrdetonia(a)protonmail.com>

7 7

Digital Ocean - running Exit node locked
by pa011 07 Oct '16

07 Oct '16

Seems like even DO is not very much in favour of running Exits any more ? Anybody made the same experience - how to handle this please ? Thanks and Regards Paul "Hello -Although we do not specifically disallow TOR exit nodes, as the account holder you are responsible for all the traffic going through your droplet (including traffic that an exit node may generate). Also be aware that we do not allow some of the traffic types that come out of a typical TOR exit node (torrents, spam, SSH probes, hacking attempts, botnets, DDoS, etc). If you are unable to stop this sort of traffic, please reconsider running a TOR exit node as it may lead to your account suspension or termination. Please refer to our Terms of Service for greater detail on this issue: https://www.digitalocean.com/legal/terms/ Best, DigitalOcean Support "

2 2

Middle Relay changed to Exit Relay Bandwidth Change
by tmbates12 07 Oct '16

07 Oct '16

Recently I enable exits on my relay and traffic seemed to jump very high compared to the almost stagnant bandwidth increase wen it was just running as a guard middle relay. I was wondering if this was normal for the traffic to jump this much. Here's the Atlas link for my relay: https://atlas.torproject.org/#details/ABF5C38A93F2D7E77A226871AB0ADB052279B…

2 1

Dealing with OVH Abuse Complaints
by teor 05 Oct '16

05 Oct '16

Hi, Does anyone have experience running a long-lived Exit on OVH / So You Start? We've just received a threat to shut down our OVH Exit due to abuse complaints. We were responding to these automated reports (mainly SSH brute force) with template responses, offering to block the destination IP and port if the remote site wanted us to. We never received a reply. What does OVH expect its Exit operators to do with complaints? Should we have blocked each complaining IP address as soon as we received a complaint? Tim T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org

8 7

TOR Services on Microsoft Azure
by Volker Mink 04 Oct '16

04 Oct '16

Hi. I read some pages on the internet about TOR-servers on cloud-services like Microsoft Azure or Amazon AWS. Just gave it a try on Azure and it works like a charm! You can sign up for free and receive credits worth ~200$. With this credits you can safely run an unlimited VPS for about 4-5 month. https://atlas.torproject.org/#details/0534295ACFD5A84312183B41D3FB275E9ADD9E E2 i think im going to give Amazon AWS also a try J regards, volker

7 11

The Onion Box v3.0: Web Interface for your Tor relay
by Ralph Wetzel 04 Oct '16

04 Oct '16

5 10