- tor-relays - lists.torproject.org

bad exit flag reason
by nusenu 24 Sep '17

24 Sep '17

Hi, [1] is not maintained since a long time. I'm curious what the reason for assigning the badexit flag to [2] was. If you know anything about it and can share something, that would be great. thanks, nusenu [2] https://atlas.torproject.org/#search/flag:badexit 37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA 37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8 [1] https://trac.torproject.org/projects/tor/wiki/doc/badRelays -- https://mastodon.social/@nusenu https://twitter.com/nusenu_

3 3

bug messages in my relay's notices.log
by Scott Bennett 23 Sep '17

23 Sep '17

I've gotten a couple of these sets of messages in the last few hours. Sep 22 05:13:17.366 [warn] tor_bug_occurred_: Bug: src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed. (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed in tor_compress_process at src/common/compress.c:576. Stack trace: (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x11a63fc <tor_bug_occurred_+268> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x11abbd4 <tor_compress_process+228> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x11ab0fa <tor_compress+554> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x11ab540 <tor_uncompress+64> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x114ecfd <connection_dir_reached_eof+1773> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x1126c43 <connection_handle_read+3027> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x106db94 <connection_add_impl+532> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x1c1e8564e <event_base_assert_ok_nolock_+3102> at /usr/local/lib/libevent-2.1.so.6 (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x1c1e80a1e <event_base_loop+1310> at /usr/local/lib/libevent-2.1.so.6 (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x106fa55 <do_main_loop+1413> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x1071e89 <tor_main+233> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x106d899 <main+25> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) Sep 22 05:13:17.366 [warn] Bug: 0x106d791 <_start+417> at /usr/local/bin/tor (on Tor 0.3.1.6-rc efc306c59aa9ee1a) My outdated system is running FreeBSD 10.3-STABLE. I've never seen these messages before that I can remember. What causes them? What, if anything, should I do about them? And what fallout do they cause for users? Thanks in advance for any relevant information! Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

3 5

tor on tails
by TorGate 23 Sep '17

23 Sep '17

Hi, can i setup a tor server with tails ? I planing 4 new tor servers TorGate1,2,3,4 . Is this a god ide ? Steffen

2 1

abuse email for non-exit relay (masergy)
by relay 000 23 Sep '17

23 Sep '17

FYI, I got this email for a non-exit relay - please share if you get them as well: To Whom it May Concern, You have a system on your network that is actively scanning and/or attacking external sites on the Internet. This can come from many sources and because it is often difficult to detect this activity, we are sending this E-mail in an attempt to help you solve the problem. We have detected your system with an IP of, <relay-IP>, scanning a client we monitor. This was not a short attack but a prolonged scan and/or probe that was designed to find and intrude into the target network. This may be someone on your network who is actively trying to hack others. This person may be a legitimate user on your network or it may be that this system has been compromised and is being used by someone to hack others. It is also likely that the system is running automated tools that have been installed to perform these actions without any human intervention. Below is the information about the attack. Keep in mind that the source IP of our client has been sanitized for anonymity. Date: 09/XX/2017 Time Zone: America/Chicago Source(s): relay-IP Type of Attack/Scan: Generic Hosts: <RFC1918 IP address> Log: relay-IP:ORPort > RFC1918 IP address Possible Cause: Thank you for your attention to this matter, Masergy email: esp(a)masergy.com mailto:esp@masergy.com ---------------

6 10

Bug Report for 3.1.7 (Debian)
by Sebastian Urbach 23 Sep '17

23 Sep '17

Good Morning, I just updated my Exit to 3.1.7 (Debian) a few hours ago and found this: [warn] tor_bug_occurred_(): Bug: ../src/common/compress.c 576: Sep 22 15:01:46.000 [warn] Bug: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *iSep 22 15:01:46.000 [warn] Bug: /usr/bin/tor(log_backtrace+0x43) [0x560c022013eSep 22 15:01:46.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0xb9) [0x560c022Sep 22 15:01:46.000 [warn] Bug: /usr/bin/tor(tor_compress_process+0x135) [0x560Sep 22 15:01:46.000 [warn] Bug: /usr/bin/tor(+0x18e715) [0x560c02223715] (on To 1Help 2Wrap 3Quit 4Hex 5Goto 6 7Search 8Raw 9Format 10Quit Please contact me for further information if needed. -- Sincerely yours / M.f.G. / Sincères salutations Sebastian Urbach --------------------------------------------------------------------------- Those who surrender freedom for security will not have, nor do they deserve, either one. --------------------------------------------------------------------------- Benjamin Franklin (1706-1790)

3 2

FallbackDirectoryMirrors selection criteria "uptime"
by Martin Kepplinger 22 Sep '17

22 Sep '17

hi, Fallback directory mirrors [1] seem to be selected (if the need should arise, according to release planning and whatnot) with criteria "uptime", among others. And it's only this criteria I'm thinking about here: Now, in the wiki we have advice on how to improve relay security, and among many, there is advice to wipe the master key / identity every 1-2 years [2]. Fallback directory mirrors are *selected* based on uptime, and *expected* to stay up, of course, for about at least 2 years. This somehow encourages to keep your identity forever. That's a contradiction and it might end up in *not* selecting relays, whos operators care a lot about security. thanks martin [1] https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2] https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity#Vector1:…

2 2

Horizons Relay Figerprint
by Kurt Besig 21 Sep '17

21 Sep '17

E65D300F11E1DB12C534B0146BDAB6972F1A8A48

3 2

Re: [tor-relays] tor-relays Digest, Vol 80, Issue 26
by flipchan 21 Sep '17

21 Sep '17

https://okservers.net/ doesn't provide vps :/ something like a good ISP that tolerate exit nodes would be good like something in holland maybe? On September 18, 2017 1:50:45 AM GMT+02:00, tor-relays-request(a)lists.torproject.org wrote: >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: Tolerant hosting for exit node. (King Queen) > 2. Re: Tolerant hosting for exit node. (Alec Larsen) > 3. Re: Tolerant hosting for exit node. (nusenu) > 4. Re: Tolerant hosting for exit node. (nusenu) > 5. Re: Tolerant hosting for exit node. (George) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Sun, 17 Sep 2017 19:59:12 +0100 >From: King Queen <kingqueenits(a)gmail.com> >To: armenian_priest <tor-relays(a)lists.torproject.org> >Subject: Re: [tor-relays] Tolerant hosting for exit node. >Message-ID: <1674967117.20170917195912(a)gmail.com> >Content-Type: text/plain; charset=us-ascii > >https://box.cock.li FTW > >yeah it's servers with cocks, but it is in Romania / IP location the >Seychelles, and I have had no issues with my exit node on them. > > > >Sunday, September 17, 2017, 11:32:33 AM, you wrote: > >> Hello list, > >> I was hoping to get a good suggestion from here for a hosting >provider >> that is tolerant with Tor exit nodes. > >> I went through the mailing list archive a few months back and there >> weren't any good suggestions on hosting providers. > >> Also, I checked the 'GoodBadISPs' page in the Tor wiki but it is >pretty >> outdated and I already got burned with one provider from there: >ITLDC, >> it was added on 2016-04-23 but they bluntly stated that they DO NOT >> tolerate exit nodes after 2 abuse complaints, my exit node was >running >> for 1 month there. > >> One of the abuses was handled but with the second one they basically >> wanted me to block HTTP/S traffic on the VPS. > >> I am not sure who edits and keeps track of the mentioned page but it >> would be a good idea to remove the mentioned provider from there so >> other people wont waste their money. > >> Hope to get some recommendations since I want to support the network >> with an exit node. > >> Thanks in advance! > >> With regards, > >> jack > > >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > >-- >Best regards, > King mailto:kingqueenits@gmail.com > > > >------------------------------ > >Message: 2 >Date: Sun, 17 Sep 2017 22:41:53 +0000 >From: Alec Larsen <aleclarsen42(a)gmail.com> >To: armenian_priest <tor-relays(a)lists.torproject.org> >Subject: Re: [tor-relays] Tolerant hosting for exit node. >Message-ID: > <CANw7z-gfKu72VkdQFL0FfZqCeMqmkqW1C3AaAjLeDcm1tsxHng(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >https://okservers.net/ is newer, but they are Tor friendly, very price >competitive, and allow payment in Bitcoin. > >On Sun, Sep 17, 2017 at 1:59 PM King Queen <kingqueenits(a)gmail.com> >wrote: > >> https://box.cock.li FTW >> >> yeah it's servers with cocks, but it is in Romania / IP location the >> Seychelles, and I have had no issues with my exit node on them. >> >> >> >> Sunday, September 17, 2017, 11:32:33 AM, you wrote: >> >> > Hello list, >> >> > I was hoping to get a good suggestion from here for a hosting >provider >> > that is tolerant with Tor exit nodes. >> >> > I went through the mailing list archive a few months back and there >> > weren't any good suggestions on hosting providers. >> >> > Also, I checked the 'GoodBadISPs' page in the Tor wiki but it is >pretty >> > outdated and I already got burned with one provider from there: >ITLDC, >> > it was added on 2016-04-23 but they bluntly stated that they DO NOT >> > tolerate exit nodes after 2 abuse complaints, my exit node was >running >> > for 1 month there. >> >> > One of the abuses was handled but with the second one they >basically >> > wanted me to block HTTP/S traffic on the VPS. >> >> > I am not sure who edits and keeps track of the mentioned page but >it >> > would be a good idea to remove the mentioned provider from there so >> > other people wont waste their money. >> >> > Hope to get some recommendations since I want to support the >network >> > with an exit node. >> >> > Thanks in advance! >> >> > With regards, >> >> > jack >> >> >> > _______________________________________________ >> > tor-relays mailing list >> > tor-relays(a)lists.torproject.org >> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> >> >> -- >> Best regards, >> King mailto:kingqueenits@gmail.com >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >

4 5

Some Dir Authorities blocked
by Graeme Neilson 20 Sep '17

20 Sep '17

Hi, I am running a relay but 4 out of 8 directory authorities appear to being blocked by my ISP. There is no route to the blocked authorities and the last responding tcp traceroute hop is an ISP machine. There are routes via IPv6 though. Is there anything I can do to get my relay in the consensus? Thanks, G

10 16

A Common Thread: Guard Status
by Kurt Besig 20 Sep '17

20 Sep '17

Just curious and I know it's probably been answered 100x times... I recently updated Tor to an, 'approved version', after 340+ days of up time. Upon restarting the relay, 25 days ago, Ive not been given the 'guard flag' again. Why? Thanks

4 4