- tor-relays - lists.torproject.org

Re: [tor-relays] tor-relays Digest, Vol 59, Issue 8
by Manager Bahia del Sol LLC 06 Dec '15

06 Dec '15

1 0

Re: [tor-relays] Unbelieveable
by Manager Bahia del Sol LLC 06 Dec '15

06 Dec '15

5 6

Unbelieveable
by Kurt Besig 06 Dec '15

06 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That I got two responses after posting to tor-relays regarding a fairly simple, I thought, CntrolPort question on a new VPS relay.. That's pathetic. Thanks for all your input. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWYP6FAAoJEJQqkaGlFNDPTCUIAKGRC9/XUKeBLrhIlXUrZd03 oTiWdNJebmCRJ55gXbXv+2VxwM18YipkkwEIRmxrSdUsvzn2zRZ11FOnv1Yi8tFY oiD8HgqLVe6pcDepslPPe/SJyMz6tIqBnosYG6yADOpYCXRR22ehRlPQHkdg2kZ+ ePBWJwDVop8WXUDwgAxRFd/jp/WWjLRt90bgHpcupEzbGi7GMTvNbftHEBeJvhwc g1xp5gZlvBgCT8Kb03dXQCUaYQ8hpjc9zbo4sQwnJNOZpyU6ftLdsoODa8NRW73s bslUj6EjQ5P2+tC2d9Q7s669XpLoxipJm1QiYVqFPIfLo48F4GjW1r64SKBxHVw= =mddV -----END PGP SIGNATURE-----

14 22

VPS Connection Refused
by Kurt Besig 04 Dec '15

04 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just set up a VPS on PulseServers as I noticed quite a few running relays had mostly good things to say about the service. So Far the people operating the servers seem very cooperative and responsive. Anyway I've been running a middle relay for 1.5 years and know the "ropes" pretty well, however a VPS is new to me. After setting up Tor and tor-arm on the VPS I'm not able to connect with this error: unable to reconnect (connection refused. Is the ControlPort Enabled?) I've edited ~/home/.arm/torrc and /etc/tor/torrc un-commenting the ControlPort 9052 and all the other typical ports, etc.. Obviously I'm not able to forward or enable ports on the VPS, so do I need to ask the admin to make some changes? Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWX3RnAAoJEJQqkaGlFNDPiS4H/2g/stKLNl0R1ZzbM2/MmC45 D0t2K8E7mcuIhxDiQJ/klaluJWnTHUrUPonSXTZuMYQJOBjdQIV6Mbq61/2g/TK9 VOdiTIsJSD30wmPIUZXlFb7xGX98DNedsySbCG4evJGmJvmEKXiAwg9i/K0iz5Ar KmRTRxtqCUJcmS+L0s0chV2A7TsIpP2h/WUS/tzc+AmAlbx1jZ4K1zu2uzCqZIjQ 69nkbbHd9DDlmSXvC9aKCB1MO3HcJUgA6gUin4UBOhkrTokbfRQBtizuHqlI4RSG sL9CyOocs9d1DEQVF1pN3PPNjWh/Owm4WzMTm3dMJ+DuRQQ5ls3R+4Fn9I//2Mg= =26fO -----END PGP SIGNATURE-----

6 11

(no subject)
by 海洋 04 Dec '15

04 Dec '15

1 0

webiron requesting to block several /24 subnet
by WubTheCaptain 03 Dec '15

03 Dec '15

This will be my lengthy opinion on Webiron to get everything out of my mind without redactions. > Webiron's system sends notifications to both the abusix.org contact > for the IP and to abuse at base-domain.tld for the reverse-DNS name of > the relay IP. This doesn't seem to be the case for us. Our rDNS is set to tor-exit.se.partyvan.eu. Back when I received our first abuse complaint from Webiron, the WHOIS for the Tor exit IP-address had an abuse-mailbox contact for us but the abuse-c was still pointed at our data center. Webiron emailed three email addresses: - abuse(a)portlane.com (abuse-c, mnt-by for all of our /29) - info(a)partyvan.eu (unlisted, unused RFC 2142 address) - abuse(a)partyvan.eu (abuse-mailbox) By the time I had received a second or third abuse report from Webiron, I had made some voluntary changes to get the abuse-c assigned to us after registering to RIPE database. Despite this, Webiron's system still contacted two addressses: - abuse(a)portlane.com (mnt-by for netnum) - abuse(a)partyvan.eu (abuse-c and abuse-mailbox) More accurately, Webiron may employ caching of results or go for the netnum abuse-c/abuse-mailbox instead. Other abuse complaints we've received such as one from the Brazilian Army have contacted our abuse@ role only and never bothered our data center. For what it's worth, abuse.net also lists our abuse@ contact for the domain. > I'm currently in the middle of a somewhat heated e-mail debate with > their vice-president. > Pasting the e-mails below would be indelicate, but their position is > that the Tor network is responsible for the abuse it generates and > should take measures to prevent/block malicious traffic. > They also state that according to their measurements, 99% of the > traffic coming out of Tor is hostile, and they're going to release a > report on the matter soon. Webiron's policies are dodgy at best. They even claim that Tor exit operators are legally liable for the traffic they route [1], which is obviously false given our real legislative liability protection for service providers. I immediately lost sense of their credibility. They say: > Groups hosting exit nodes are responsible for the abuse that comes out > of exit nodes. By refusing to take action to stop attacks originating > from your proxies it can make you legally responsible to international > law as well as laws in most regions (IE EU) as it shows a willingness > to facilitate further attacks. Our data center doesn't seem to mind Webiron's abuse reports regarding our Tor exit, and while they also get copies of the abuse complaints they've never bothered us about it. (For the curious, Portlane used to house Serious Tubes which housed The Pirate Bay until a raid on December 2014.[2]) After receiving six or so abuse complaints from Webiron [3] and acknowledging each to support(a)webiron.com explaining it's a Tor exit, I've not heard back from them again for a while. Banning /32 or /24 seems out of question for us to keep the limited liability protection. It wouldn't solve the issue anyway due to 1000+ other exits available, so the best solution remains to block Tor temporarily from the other end or implement CAPTCHAs for Tor users to slow down or defeat bruteforce attacks. As an example, CloudFlare implements CAPTCHA for visitors from Tor. Webiron could do something similar if they wished to act on these as a reverse proxy service. Their requests are too unreasonable for Tor exit operators. By their ideology, I understood they're saying stores selling ski equipment for skiing should be held liable for crimes commited by their customers who bought their skiing masks: > You chose to allow this to run from the network you are responsible > for. Proxing attacks is translatable to providing the mask before an > assault or robbery. At this point we feel your company is complicit in > these attacks by allowing them to continue. For me this does not sound credible, and I didn't bother trying to give their argument more credibility with a reply. They wished me "good luck" [4] after mentioning my Tor exit will be on their blacklist and referencing to IBM's research on "recommending a blanket ban on Tor".[5] At least I still remain to have some sense of credibility in SpamCop and Spamhaus, despite few controversies involved with the latter. This is why we can't have nice things and why I've given up with most hosting providers. PS: Portlane is not yet listed on GoodBadISPs [6] wiki page. -Wub [1]: https://archive.is/Obhnk [2]: http://www.bbc.com/news/technology-30411782 [3]: https://partyvan.eu/transparency/emails/abuse/ [4]: https://partyvan.eu/transparency/emails/abuse/2015-11-13-webiron-tor-exit.m… [5]: http://www.techweekeurope.co.uk/security/ibm-companies-tor-175468 [6]: https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs

1 0

PASSWORD
by John favino 29 Nov '15

29 Nov '15

I NEVER RECEIVED A PASSWORD.

3 2

Re: [tor-relays] webiron requesting to block several /24 subnet
by Dhalgren Tor 28 Nov '15

28 Nov '15

>. . .I have to understand how my ISP reacts to this kind of things. >For the moment I will keep a low profile and I will block the >mentioned IP range for a month. Webiron's system sends notifications to both the abusix.org contact for the IP and to abuse(a)base-domain.tld for the reverse-DNS name of the relay IP. So if you can configure abuse@ for the relay domain to forward to you, you will see their notices at the same time as the ISP abuse desk. Might be helpful to know about it before they contact you and/or to see if they become familiar enough with the notices to ignore them. Automated abuse complaints from other sources do not always go to the domain-based address. http://multirbl.valli.org/ is a handy resource that shows the abuseix.org and abuse.net information, as well as how many DNSBLs the relay has racked up. You can change the abuse.net contact but Webiron appears to ignore this source and simply construct the abuse@ from the rDNS domain name.

7 8

Any experience with Pulse Servers?
by Jesse V 28 Nov '15

28 Nov '15

Hi everyone, I've been looking around for a new host for my Tor infrastructure, which includes exits, relays, and a bridge. I've been reviewing https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs and ran across Pulse Servers, which seems Tor friendly. They have VPSs in Canada and the UK and have really low prices on VPSs, which I'm trying to understand. I've been trying to learn more but I think they have a pretty small setup (apparently the owner does tech support) and documentation is limited. Does anyone have any experience or opinions on them? -- Jesse V

4 3

Arm thinks Tor is not running as a Daemon?
by Jannis Wiese 27 Nov '15

27 Nov '15

Hi, I’m a bit confused right now. I’ve upgraded my relay to Debian Jessie yesterday and since then, arm keeps telling me > [ARM_WARN] The torrc differs from what tor's using. You can issue a > sighup to reload the torrc values by pressing x. > - configuration value is missing from the torrc: RunAsDaemon I’m running the same configuration as before (running Debian Wheezy), where it worked without any warning. RunAsDaemon is set to 1 in tor-service-defaults-torrc, still arm is showing me on the Tor configuration page “RunAsDaemon False”. Putting RunAsDaemon into torrc as well triggers this: > [ARM_WARN] The torrc differs from what tor's using. You can issue a > sighup to reload the torrc values by pressing x. > - torrc value differs on line: 17 The problem here: There is no line 17 in my torrc… I’ve already read tickets like #16459[1] and #2501[2] but it didn’t help much. Damian says in Ticket #16459 > […] This message is meant to help people who edit their torrc, forget to restart tor, and are then confused why the settings didn't take effect. [...] I did restart tor (a couple times) and apparently it is running as a Daemon (service --status-all). So I hope this is “just” an issue with arm… Maybe someone of you has an idea? I’m running arm 1.4.5.0 and tor 0.2.7.5 (from deb.torproject.org <http://deb.torproject.org/>) Cheers, Jannis [1] https://trac.torproject.org/projects/tor/ticket/16459 [2] https://trac.torproject.org/projects/tor/ticket/2501

2 2