- tor-relays - lists.torproject.org

Re: [tor-relays] Possible to run a tor bridge/relay via tor browser?
by Keifer Bly 30 Mar '20

30 Mar '20

2 1

Moving my obfs4 bridge from tor expert bundle to Debian, and have some questions. Thanks.
by Keifer Bly 30 Mar '20

30 Mar '20

Hi all, So I am switching the OBFS4 bridge I was running via Tor Expert Bundle on Windows 10 over to running it via Debian app for Windows 10. This app is on the Windows store at https://www.microsoft.com/en-us/p/debian/9msvkqc78pk6?activetab=pivot:overv… Essentially, it is an app that lets you run Linux packages on Windows. I made the switch so that I could keep tor and obfs4 up to date using unattended upgrades. However, for some odd reason, despite the fact I backed up the tor identity keys and pasted them into the keys directory when I moved over, the bridge is still generating new keys on startup. I copied the key files from my expert bundle bridge to /var/lib/tor/keys directory in the Linu terminal, I copied all of the files. It’s a bridge so no big deal I guess, but wonder why that is happening. https://metrics.torproject.org/rs.html#details/780F4E3ADBC574A63CE8155C0911… And, I tested to see of unattended upgrades was working correctly after configuring it with these instructions: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpd… And got this the attached photo as a result, does this mean it is keeping tor and obfs4 up to date? Thanks very much. tor update test.PNG <https://drive.google.com/file/d/1c5TinBlApx5YuObiwt8pkl9w_F74O0JL/view?usp=…> --Keifer

2 4

BadExit
by gerard＠bulger.co.uk 30 Mar '20

30 Mar '20

Oh the shame! Never had that tag on my exit before. I assume it was due to a bad boy attacking an IP, pointed out by my ISP, and the ISP put my server "under mitigation". I assume some filtering, which of course would have looked bad to TOR users. I did not spot the ISP's email for 30 minutes, but then I was able to block the offended IP. Within minutes of doing that the ISP said attack stop and my server was removed from mitigation. However the next day badexit tag on my exit and remains there How long does the tag last? I go to my other, overseas exit, a family member, to see the tag is aslo applied there to. Do family members get tarred with the same brush? I have turned both into relays for the time being. Or have I got this wrong. Is it a DNS thing? Are no some DNS providers causing issues forcing the tag? I am not using opendns. Gerry

5 12

Moving my obfs4 bridge from tor expert bundle to Debian
by Keifer Bly 30 Mar '20

30 Mar '20

1 0

Possible to run a tor bridge/relay via tor browser?
by Keifer Bly 30 Mar '20

30 Mar '20

2 3

Problem with ubuntu 18.04 x386
by Francisco 30 Mar '20

30 Mar '20

I make the installation following the official page torproject.org from the tor repositories. I edit de torrc file and save the changes. but when i restart the service, gives me error. $ systemctl status tor@default failed (Result: exit-code) since... systemd[1]: tor(a)default.service: Start request repeated too quickly. systemd[1]: tor(a)default.service: Failed with result 'exit-code'. systemd[1]: Failed to start Anonymizing overlay network for TCP. thanks in advance. Sent from ProtonMail mobile

5 4

Re: [tor-relays] Problem with ubuntu 18.04 x386
by Francisco 30 Mar '20

30 Mar '20

Hi, sorry for that, I'm sending more information now: Tor version: Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. The log when I try to restart the service (sudo systemctl restart tor@default) : Job for tor(a)default.service failed because the control process exited with error code. See "systemctl status tor(a)default.service" and "journalctl -xe" for details. $ systemctl status tor(a)default.service tor(a)default.service - Anonymizing overlay network for TCP Loaded: loaded (/lib/systemd/system/tor(a)default.service; enabled-runtime; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-03-29 14:25:21 -03; 4min 55s ago Process: 2587 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --ver Process: 2586 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /run/tor (code=exited, status=0/SUCCESS) mar 29 14:25:21 x systemd[1]: Failed to start Anonymizing overlay network for TCP. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Service hold-off time over, scheduling restart. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Scheduled restart job, restart counter is at 5. mar 29 14:25:21 x systemd[1]: Stopped Anonymizing overlay network for TCP. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Start request repeated too quickly. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Failed with result 'exit-code'. mar 29 14:25:21 x systemd[1]: Failed to start Anonymizing overlay network for TCP. $ journalctl -xe mar 29 14:25:21 x systemd[1]: tor(a)default.service: Failed with result 'exit-code'. mar 29 14:25:21 x systemd[1]: Failed to start Anonymizing overlay network for TCP. -- Subject: Unit tor(a)default.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit tor(a)default.service has failed. -- -- The result is RESULT. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Service hold-off time over, scheduling restart. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Automatic restarting of the unit tor(a)default.service has been scheduled, as the result for -- the configured Restart= setting for the unit. mar 29 14:25:21 x systemd[1]: Stopped Anonymizing overlay network for TCP. -- Subject: Unit tor(a)default.service has finished shutting down -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit tor(a)default.service has finished shutting down. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Start request repeated too quickly. mar 29 14:25:21 x systemd[1]: tor(a)default.service: Failed with result 'exit-code'. mar 29 14:25:21 x systemd[1]: Failed to start Anonymizing overlay network for TCP. -- Subject: Unit tor(a)default.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit tor(a)default.service has failed. -- -- The result is RESULT. mar 29 14:29:38 x kernel: perf: interrupt took too long (3160 > 3140), lowering kernel.perf_event_max_sample_rate to 63250 mar 29 14:30:17 x sudo[2616]: fcp : TTY=pts/0 ; PWD=/home/fcp ; USER=root ; COMMAND=/bin/systemctl status tor@default mar 29 14:30:17 x sudo[2616]: pam_unix(sudo:session): session opened for user root by (uid=0) mar 29 14:32:07 x sudo[2616]: pam_unix(sudo:session): session closed for user root Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, March 29, 2020 9:00 AM, <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. Problem with ubuntu 18.04 x386 (Francisco) > 2. Re: Problem with ubuntu 18.04 x386 (TorGate) > > > Message: 1 > Date: Sun, 29 Mar 2020 06:31:48 +0000 > From: Francisco franciscort(a)protonmail.com > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] Problem with ubuntu 18.04 x386 > Message-ID: > TmgFQrqhT-AZx7PXSZ5VGxxkmeI-Xf869hC1IKYE6itAhAZwpgjfJ-jkkcNCKUNC4GaHzRi4gLCO91k1K9xPRajp-5hAg6aJEYUFvoNvPtc=(a)protonmail.com > > Content-Type: text/plain; charset="utf-8" > > I make the installation following the official page torproject.org from the tor repositories. > > I edit de torrc file and save the changes. but when i restart the service, gives me error. > > $ systemctl status tor@default > failed (Result: exit-code) since... > > systemd[1]: tor(a)default.service: Start request repeated too quickly. > systemd[1]: tor(a)default.service: Failed with result 'exit-code'. > systemd[1]: Failed to start Anonymizing overlay network for TCP. > > thanks in advance. > > Sent from ProtonMail mobile >

2 1

Re: [tor-relays] Possible to run a tor bridge/relay via tor browser?
by Keifer Bly 27 Mar '20

27 Mar '20

1 0

New relay
by William Pate 27 Mar '20

27 Mar '20

Set up another relay (this time on Raspberry Pi 4): https://metrics.torproject.org/rs.html#details/BD187CF1B44A84EC7DD1BC2AC9C4… William Pate willpate(a)pm.me 512-947-3311 inadequate.net

2 2

tor on Centos version question
by torix＠protonmail.com 24 Mar '20

24 Mar '20

I can see that my Debian relay went from 0.4.2.6 to 0.4.2.7 a few days ago automatically with auto updates set up. However, my hosted relay, which runs on Centos 7, is still at version 0.3.5.8. I am using the epel repo version. Is that okay? Or should I have added a tor repo? TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1