- tor-relays - lists.torproject.org

OpenBSD -stable net/tor and 0.4.7.7
by George 10 May '22

10 May '22

The OpenBSD net/tor -current port is correctly on 0.4.7.7, but the -stable port is still on 0.4.6.10. I submitted a diff to update -stable port to 0.4.7.7 last week, but it has not been committed yet. https://marc.info/?l=openbsd-ports&m=165179875418235&w=2 It's attached and should work fine. In order to update the OpenBSD -stable port you need an updated -stable 7.1 ports tree, then you apply the patch within the /usr/ports/net/tor port, and build from there. I can provide more guidance if necessary, but in order to not bore everyone else, maybe the Tor-BSD list is more appropriate? https://lists.nycbug.org:8443/mailman/listinfo/tor-bsd I can send out an amd64 -stable package, but then you'd have to trust me. g

1 0

Bridge not used
by Arnim Wiezer 10 May '22

10 May '22

Hi Tor-Operators, I have installed a bridge according to the official how-to. The config is as follows: Log notice file /var/log/tor/notices.log DataDirectory /var/lib/tor Address bridge.xxx.de BridgeRelay 1 ORPort 1044 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:9043 ExtORPort auto ContactInfo arnimw(a)mailbox.org Nickname lunabridge PublishServerDescriptor 1 BridgeDistribution any Under https://metrics.torproject.org/rs.html#details/4DD98FB1959065309FD4A183530B… I see basically no usage, the logs are fine - as far as I can tell. Any help appreciated! Best, Arnim

3 4

Tor 0.4.7.7 Segmentation fault on Ubuntu 22.04 caused by "rseq"
by Xiaoqi Chen (Danny) 07 May '22

07 May '22

Dear relay operators, I recently upgraded one of my relays to Ubuntu 22.04 and now tor keeps crashing. I debugged a little bit and saw the following error in the log. It appears that it's due to seccomp not allowing "rseq" syscall, and possibly related to the latest version of Glibc. I temporarily mitigated the issue by turning off sandbox mode (remove "Sandbox 1" in torrc). Does anyone know how to properly resolve the crashing issue? Cheers, Danny Chen -- $ sudo tor -f /etc/tor/torrc May 07 02:10:46.831 [notice] Tor 0.4.7.7 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc. ...... May 07 02:10:46.833 [notice] Opening Directory listener on 0.0.0.0:8080 May 07 02:10:46.833 [notice] Opened Directory listener connection (ready) on 0.0.0.0:8080 Fatal glibc error: rseq registration failed ============================================================ T=Fatal glibc error: rseq registration failed 1651889448 Tor 0.4.7.7 died: Caught signal 11 Fatal glibc error: rseq registration failed Fatal glibc error: rseq registration failed tor(+0xee525)[0x55c6431d6525] /lib/x86_64-linux-gnu/libc.so.6(abort+0x178)[0x7fe6da9ee898] /lib/x86_64-linux-gnu/libc.so.6(abort+0x178)[0x7fe6da9ee898] /lib/x86_64-linux-gnu/libc.so.6(+0x8945c)[0x7fe6daa4f45c] /lib/x86_64-linux-gnu/libc.so.6(+0x89770)[0x7fe6daa4f770] /lib/x86_64-linux-gnu/libc.so.6(+0x94b31)[0x7fe6daa5ab31] /lib/x86_64-linux-gnu/libc.so.6(+0x126a00)[0x7fe6daaeca00] Fatal glibc error: rseq registration failed

4 3

Relay Throttling
by sysmanager7 06 May '22

06 May '22

Hi Is there a tutorial on how to limit a relay's throughput?? There has to be! I did a search and came up empty. I'm trying to avoid shutting down my relay's due to financial burden Any help would be appreciated. Thank you! Sent with [ProtonMail](https://protonmail.com/) secure email.

5 4

Re: [tor-relays] Relay Throttling
by me＠mirandaniel.com 06 May '22

06 May '22

Hey, check your torrc, there is a RelayBandwidthRate setting (to limit speed) and also an AccountingMax setting to limit max traffic per month. -- MiranDaniel "---------- Původní zpráva ---------- Od: sysmanager7 via tor-relays <tor-relays(a)lists.torproject.org> Datum: 06.05.2022 14:16:35 Předmět: [tor-relays] Relay Throttling Hi Is there a tutorial on how to limit a relay's throughput?? There has to be! I did a search and came up empty. I'm trying to avoid shutting down my relay's due to financial burden Any help would be appreciated. Thank you! Sent with ProtonMail(https://protonmail.com/) secure email. "

1 0

Tor Exit: Complaints of IP being used for "spam" despite exit policy
by Neel Chauhan 05 May '22

05 May '22

Hi, A day or two ago, my Tor exit host, Psychz Networks, has sent me complaints about my IPs being used to send "spam" despite me having blocked Port 25 (and 465/587) in the exit policy. Psychz threatened to block Port 25 even when my exit policy explicitly blocks 25/465/587. The URLs I got were from Cisco Talos: * https://talosintelligence.com/reputation_center/lookup?search=104.149.136.2… * https://talosintelligence.com/reputation_center/lookup?search=104.149.133.5… Sometimes I think "is my FreeBSD exploited and being used to send spam", but then I also see Linux relays on other ISPs also on the blocklists. Yes, I am aware Tor exit relays will land on blacklists. But getting complaints from spam is new, especially when my relays are blocking SMTP. I am worried I would have to find a new host if they continue complaining. Darn, Psychz has been one of the more reliable exit hosts (on-and-off) for many years, although they are more vigilant on abuse than say BuyVM. BuyVM is similarly priced (although my Psychz is an special offer) and solid but has too many exits. OVH and TerraHost only allow exits on much more expensive dedicated servers. Prgmr and HostMaze allow exits but has so-so peering. I just hope Psychz doesn't continue to complain. -Neel

5 7

comments, hints and tipps for an ansible role to deploy Tor bridges
by Toralf Förster 04 May '22

04 May '22

I do appreciate those for my attempt here: https://github.com/toralf/tor-relays TIA -- Toralf

2 1

BSD tor ports/packages and impending 0.4.7.7 release
by George 03 May '22

03 May '22

BSD relay operators, like everyone else, should be aware that upgrading tor to 0.4.7.7 is critical for exit relays. The source is available now at: https://dist.torproject.org/tor-0.4.7.7.tar.gz Specifically for the BSD ports, here is the current status and workings. Any corrections appreciated. * DragonflyBSD https://github.com/DragonFlyBSD/DPorts/tree/master/security/tor Downstreams from FreeBSD quarterly updates, so may not have a 0.4.7.7 package or port for security/tor until July. * FreeBSD https://www.freshports.org/security/tor https://cgit.freebsd.org/ports/tree/security/tor https://svnweb.freebsd.org/ports/head/security/tor/ Updated to 0.4.7.7 already, and can be installed from security/tor now. Working fine at this point. For pkg(8) users, ensure that /etc/pkg/FreeBSD.conf line 11 is set to "latest", as opposed to "quarterly", which should be the case regardless of this security/tor release: url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", * NetBSD https://pkgsrc.se/net/tor pkgsrc's current port of net/tor was updated to 0.4.7.7. The stable port is still on 0.4.6.10 at https://cdn.netbsd.org/pub/pkgsrc/stable/pkgsrc/net/tor/Makefile * OpenBSD https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/tor/ The -current net/tor has been updated to 0.4.7.7 and the package is available. For users running 7.1-stable, net/tor 0.4.7.7 will hopefully be officially backported. Users can also update net/tor from ports on -stable themselves easily enough. If you're not on 7.1-stable, consider upgrading immediately. Thanks. g

1 0

Possible Connection Storm
by Eddie 26 Apr '22

26 Apr '22

Checking my relays after being away for a few days, noticed that one of them was showing as Overloaded, which I've never seen in over a year's running. Looking in the logs, it looks like there was a huge increase in connections, which has now settled down and I'm no longer showing as overloaded. Here's some relevant pieces: Apr 21 03:45:08.000 [notice] Heartbeat: Tor's uptime is 110 days 12:00 hours, wi th 6977 circuits open. I've sent 5236.04 GB and received 5121.19 GB. I've receiv ed 5232797 connections on IPv4 and 269395 on IPv6. I've made 2018765 connections with IPv4 and 580408 with IPv6. Apr 21 03:45:08.000 [notice] Circuit handshake stats since last time: 1901/1901 TAP, 244943/244943 NTor. Apr 21 07:04:49.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config opti on or choosing a more restricted exit policy. Apr 21 09:45:08.000 [notice] Heartbeat: Tor's uptime is 110 days 18:00 hours, wi th 47998 circuits open. I've sent 5263.73 GB and received 5148.85 GB. I've recei ved 5244063 connections on IPv4 and 270025 on IPv6. I've made 2021914 connection s with IPv4 and 581488 with IPv6. Apr 21 09:45:08.000 [notice] Circuit handshake stats since last time: 1609/1609 TAP, 6391488/6532508 NTor. Apr 21 15:45:08.000 [notice] Heartbeat: Tor's uptime is 111 days 0:00 hours, wit h 45439 circuits open. I've sent 5300.03 GB and received 5185.19 GB. I've receiv ed 5253283 connections on IPv4 and 270537 on IPv6. I've made 2024515 connections with IPv4 and 582464 with IPv6. Apr 21 15:45:08.000 [notice] Circuit handshake stats since last time: 467/467 TA P, 9937327/9984534 NTor. Is this anything I need to be concerned about, or is it just one of things that occasionally happens. Cheers.

2 1

Re: [tor-relays] Bridge Distribution Mechanism none
by Ross Camm 21 Apr '22

21 Apr '22

I have no error from Apparmor and I dont believe obfs4 proxy is the issue as I have obfs4 installed and confirmed running dpkg -l | grep obfs4 ii obfs4proxy 0.0.7-4 ps ax | grep obfs4 5501 ? Sl 0:01 /usr/bin/obfs4proxy netstat -nap | grep obfs4 tcp 0 0 X.X.X.X:12345 0.0.0.0:* LISTEN 5501/obfs4proxy Tor logs Apr 18 17:00:33 pi Tor[5497]: Registered server transport 'obfs4' at 'X.X.X.X:12345' torrc ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 X.X.X.X:12345 [ https://bridges.torproject.org/scan/ ]( https://bridges.torproject.org/scan/ ) also reports my ORPort is reachable via IPv4 and IPV6 Tor logs Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort [X:Y:Z::A]:993 is reachable from the outside. Excellent. Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort A.B.C.D:993 is reachable from the outside. Excellent. Publishing server descriptor. What am I missing ? Thanks again Ross > Probably because obfs4 is not installed or not running properly.> Check your logs for obfs4 errors, and for Apparmor error messages as well.> On Mon, Apr 18, 2022 at 09:07, Ross Camm <ross(a)whyza.net> wrote:> I have been up and running with my Tor Bridge for a number of months now, yet Tor Metrics reports that the Bridge Distribution Mechanism for my server is stuck on 'none'.>> Consequently I see no incoming connections to my Bridge.>> I have tried altering the following>> BridgeRelay 1>> PublishServerDescriptor bridge> BridgeDistribution moat>> with no success.>> The mechanism is always none....and I have left the changes for a week to see if Metrics updates to no avail.>> I have a static IPv4 address and functional IPv6 and have confirmed my ports are publicly accessible for both protocols>> Self-testing indicates your ORPort [XXXX:XXXX:XXXX::XXX]:993 is reachable from the outside. Excellent.> Self-testing indicates your ORPort XXX.XXX.XXX.XXX:993 is reachable from the outside. Excellent. Publishing server descriptor.>> I am running raspberry pi os buster which had an obsolete Tor version.>> I subsequently upgraded and stay up to date with the latest bullseye version via bullseye backports,>> Currently Tor 0.4.6.10-1~bpo10+1>> Any ideas of why my servers Bridge Distribution Mechanism is always reported and behaving as none ?>> Thanks in advance ;)>> Ross

2 1