- tor-relays - lists.torproject.org

Re: [tor-relays] Tor on Rpi
by relay.jackash＠simplelogin.fr 09 Feb '21

09 Feb '21

Hello Patrice would be great if you can share your script , thanks.

1 0

Can't connect to bridge after rebuilding server
by Eddie 09 Feb '21

09 Feb '21

I had to rebuild my VPS today. Before doing so, I copied off everything I thought I needed to rebuild my bridges. Following the rebuild, the bridges appear to start correctly, according to both the logs and https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However attempting to connect via the tor browser from my home system just hangs. The ports on the VPS are open. I can see an ESTABLISHED connection from home, but the browser just hangs throwing out this: [WARN] Proxy Client: unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure") Not sure what to check next.

2 3

key server error
by tor 09 Feb '21

09 Feb '21

Hello When I do the following command: :~ $ sudo gpg --keyserver keys.gnupg.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 I get: gpg: packet(13) too large gpg: read_block: read error: Invalid packet gpg: no valid OpenPGP data found. gpg: Total number processed: 0 thoughts? -matt

3 2

Tor on Rpi
by relay.jackash＠simplelogin.fr 09 Feb '21

09 Feb '21

Hello im running a tor relay on rpi 2 with version 0.4.2.7., on the Tor relay search i see my relay is outdated and flaged as not recomended, however on rpi i have tried update and upgrade many times and always get notification from apt that tor i already de newest version, also tried apt dist-upgrade but no luck. Any way to get the last version and get ride of not recomended flag from my relay? Thanks in advanced

2 1

Re: [tor-relays] Tor on Rpi (relay.jackash@simplelogin.fr)
by Patrice Bönig 08 Feb '21

08 Feb '21

Hi, I am also have a tor relay running, but on a RPI 4. No long time ago I stood at the same point as you are now. I than wrote me a skript, where it: 1. pulls the latest source 2. backs up the old data (identity) 3. compiles and installs tor 4. copies the old data on the new installation 5. adds tor to crontab 6. starts tor I think you must change some things to your need if you want to use it. If you want the script I can share it here, if it is allowed. If not I can send it to you via mail. regards Patrice > Hello > im running a tor relay on rpi 2 with version 0.4.2.7., on the? Tor relay search i see my relay is outdated and flaged as not recomended, however on rpi i have tried update and upgrade many times and always get notification from apt that tor i already de newest version, also tried apt dist-upgrade but no luck. > > Any way to get the last version and get ride of not recomended flag from my relay? >

1 0

Tor Time Logging
by Kathi 05 Feb '21

05 Feb '21

How do I change the time on my tor relay to local time? I'm not into the military/UTC thing at all. It's actually annoying for me. thanks for help!!

3 2

Possible (D)DoS attack on my relay michaelscott (47E1157F7DA6DF80EC00D745D73ACD7B0A380BCF)
by William Kane 04 Feb '21

04 Feb '21

Hi community, Unfortunately my otherwise stable tor guard relay has recently lost it's guard flag, once again, due to what I think is a new type of (D)DoS attack, either directly targeted towards my tor relay, or against some other relays inside the network, facilitated through my relay. It all started to go downhill one month ago, on January 10th of this year - the linux kernel OOM killer decided to reap the tor process, multiple times in a row - it was violating the MaxMemInQueues setting of 732MB, the optimal value according to tor - on a virtual machine with a dedicated CPU core (and sadly, a lack of hardware AES acceleration, but that's off topic, by completely sandboxing and isolating the tor process, and then disabling all mitigations offered by the linux kernel, I still managed to achieve a peak throughput of 10mb/s while keeping other users and processes safe and sound - this made the relay the fastest tor relay belonging to my AS.. sorry, just bragging ;-)) which has 1024 megabytes of physical ram, and a swap partition with a size of 512 megabytes (vm.swappiness initially was 90, I've changed it to 70). The first time this happened, it came out of nowhere, so I wasn't closely monitoring the metrics page of my relay - this led to a downtime of 3 days, then leading to the loss of the guard flag. Since then, traffic on my relay has been limited to traffic coming from other relays, it is now exclusively a middle-only relay - it did not recover from the attack, even though I managed to achieve longer consecutive uptimes by tweaking MaxMemInQueues, first down to 704, then 672, and now 640MB. The only log entry I ever saw before the tor process got reaped is the following one: Feb 04 12:47:08 *hostname_redacted* tor[224]: Feb 04 12:47:08.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [93409 similar message(s) suppressed in last 60 seconds] Feb 04 12:48:08 *hostname_redacted* tor[224]: Feb 04 12:48:08.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [42527 similar message(s) suppressed in last 60 seconds] As you can tell by the date, this was today - after 3 weeks and 1 day, this noon, the process got OOM-killed again - I instantly noticed it, logged into the machine, installed updates, updated my pacman mirrorlist, the usual stuff - then I rebooted the machine, only to log in 5 minutes later to see tor using 100% of CPU time, with the log file getting spammed by this error - it started only 3 seconds after the relay published it's descriptor. Clearly, this is some sort of targeted attack against either my relay or someone is abusing it to attack someone or something else inside or outside the tor network. I did read the recent information on attacks regarding DirAuth's, but apparently a fix has been deployed on all of them, and checking the bandwidth stats of some of them, it seems to be working, somewhat. I wonder if this is the culprit here, this machine has been running tor relays since 2014, and I never had these problems with it before - even without lowering MaxMemInQueues. To me, that's just further proof that this is a targeted attack using my relay and before you ask, I know some KVM hypervisors are oversold, but my hosting company stopped selling KVM machines with mechanical host HDD's a few years ago, so new customers can't be the reason for all of this. Is there anything I can do to make my relay as stable as possible until the attacker(s) stop(s) hammering my relay? This doesn't seem to get caught by the built-in DoS prevention, so I didn't try tweaking the associated config options. Maybe someone from the tor team has a patch I can try applying? I'm not completely up to date on the newest tor shenanigans and pitfalls, so maybe it has already been posted on this mailing list, but I don't feel like reading a bazillion messages. For the time being, MaxMemInQueues will stay at 640 megabytes, to (hopefully) at least keep the relay up and running, even though performance, for anyone unlucky enough to build a circuit through it, will be affected, severely (despite all this, I'm still pushing around 11TB/s of traffic a month, I just don't know how much of it is legitimate..) - it's my duty as a relay operator to guarantee for the safety and usability of my tor relay, so I'm very eager to find a solution for this. Unfortunately, this is a live relay, otherwise I would probably try developing my own solution for the problem (including publishing it / making a pull request), but in this case repeated downtimes and restarts, which would be necessary when working on the source code, is absolutely not an option as it would possibly disrupt hundreds, if not thousands of clients. If anyone could point me in a direction, I'd really appreciate it. Thank you, William

1 1

sig ver error and more
by tor 04 Feb '21

04 Feb '21

Hi All, So everything had been working for over a year. Am currently on tor 4.2.7, stretch. When I went to update, I got: The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 < http://deb.torproject.org/> deb.torproject.org archive signing key My deb.torproject.org--keyring is version 2018.08.06 Is this the latest version? In trying to update deb.torproject.org--keyring, it says I'm on the latest, In trying: sudo apt-key adv --recv-keys --keyserver keys.gnupg.net 74A941BA219EC810 I get: packet too large invalid packet no valid openpgp data found Maybe I used the wrong key in the above command? thoughts? -matt

1 0

Exit relay operators please help test #2667 branch
by Roger Dingledine 04 Feb '21

04 Feb '21

Hello friendly relay operators, Another day, another weird thing with the Tor network. This time we have some jerk bombing the directory authorities with directory fetches, and doing it via exits: https://lists.torproject.org/pipermail/network-health/2021-January/000661.h… The network is mostly holding together, but I wouldn't say it is pretty. One of the long-term fixes will be ticket #2667: https://gitlab.torproject.org/tpo/core/tor/-/issues/2667 where exit relays refuse to let users connect back into the Tor network. David and I made a branch this evening that implements #2667, and it could use some testing. If you're comfortable building your exit relay from a git branch, please do, and let us know how it goes. It is the "ticket2667" branch on either https://git.torproject.org/user/arma/tor or https://gitlab.torproject.org/arma/tor/ And if your relay is currently using 100% cpu and/or way more bandwidth than usual, you might be especially excited to try out this patch. :) When the defense triggers, you will see an info-level log line like "%s tried to connect back to a known relay address. Closing." (where %s is the destination, so don't get upset at them. :) You can let us know how it's going either by mail just to me, or by a reply on the list, whichever you prefer. Once we know that you're running the branch, we can also probe your relay remotely to verify that it is correctly refusing those connections. Thanks! --Roger

4 6

Sig ver error
by tor 03 Feb '21

03 Feb '21

Hi all, I'm getting a signature verification error: $ sudo apt-get update Hit:1 http://mirrordirector.raspbian.org/raspbian stretch InRelease Hit:2 http://archive.raspberrypi.org/debian jessie InRelease Get:3 https://deb.torproject.org/torproject.org stretch InRelease [3528 B] Err:3 https://deb.torproject.org/torproject.org stretch InRelease The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 deb.torproject.org archive signing key Fetched 3528 B in 3s (998 B/s) Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.torproject.org/torproject.org stretch InRelease: The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 deb.torproject.org archive signing key W: Failed to fetch https://deb.torproject.org/torproject.org/dists/stretch/InRelease The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 deb.torproject.org archive signing key W: Some index files failed to download. They have been ignored, or old ones used instead. Any thoughts would be appreciated. thanks, matt

3 2