- tor-relays - lists.torproject.org

metrics
by Manager 21 Feb '21

21 Feb '21

2 1

relayor v21.0.0 is released
by nusenu 20 Feb '21

20 Feb '21

Hi, relayor v21.0.0 is released. relayor is an ansible [1] role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor [1] https://www.ansible.com/ This version contains a bugfix: * the GPG key for deb.torproject.org expired and we shipped the expired version, we now fetch the public key directly from torproject.org instead of shipping it with the ansible role. The relayor signing key itself has also been updated: https://keys.openpgp.org/search?q=A7B5DB91CE04C9E0BE66446B8CBE52BD4D705DE9 https://github.com/nusenu/ansible-relayor/releases/tag/v21.0.0 kind regards, nusenu -- https://nusenu.github.io

1 0

TOR Exit Relay Bandwidth Drop
by pimpnet 19 Feb '21

19 Feb '21

I run a fast tor exit relay. It goes to 100MB/s easy after a few days but every 2 weeks something happens (no hardware/network issue on this node locally) and the tor bandwidth drops down to 1-2MB/s. Then I have to stop the tor service and start it again after a couple mins. Most of the times, I am not aware this has happened and the exit relay then takes 10 days to start pumping full bandwidth again The server runs Ubuntu 18.04 LTS Seeking advice from some big brains here, thanks.

1 0

orport
by Anonforpeace 18 Feb '21

18 Feb '21

Hello: Am trying to configure my bridge according to instructions on Tor site. Using Ubuntu. No matter what port I pick for the ORPort I keep getting this error: Unable to find IPv4 address for ORPort 80. You might want to specify IPv4Only to it or set an explicit address or set Address. Have never seen this before. Please help. Thanks

3 4

Optimizing Tor Relay
by friendlyexitnode 18 Feb '21

18 Feb '21

Hello everyone, I'm running a very small family of exit nodes (who are friendly) and was curious if anyone had any advice on ways to optimize their relay configuration? I'm running them all on Ubuntu 20.04. I've reviewed the [Arch Wiki,](https://wiki.archlinux.org/index.php/Tor#+100Mbps_Exit_Relay_configu… but didn't notice much of an improvement. Anyone have an advice to improve Tor performance for relays? - The Friendly Exit Node Family

2 1

Is my relay broken? No stable, hsdir or guard flags
by raltullou＠posteo.org 17 Feb '21

17 Feb '21

Hi, I'm looking for help because I can't figure out what's going on. https://metrics.torproject.org/rs.html#details/11DF0017A43AF1F08825CD5D9732… - At the beginning of January the relay seems to have lost the guard flag - A week ago I checked and noticed that the relay had also lost the stable flag despite having an uptime of >2 months at that point - A week ago I rebooted the server but the situations hasn't changed - flags are still gone - metrics.torproject graphs show that the server has been transmitting data the entire time - so it doesn't seem like I missed some downtime - Serverlogs show no problems - Relay has been running continuously for almost 4 years and only gets rebooted for kernel/tor upgrades -> so uptime and MTBF should not be a problem Is there a problem on my side? Is there anything I can do or check? It is a fallback relay - is it still useful as such? TY

4 7

Huge increase in bridge connections
by Eddie 14 Feb '21

14 Feb '21

Just trying to understand if this is normal or if something else is going on. I have 2 bridges on a VPS. One is designated as "moat", the other "email". Until earlier today, for over a year, both averaged under 10 unique clients, per 6-hour reporting period. Today, the "moat" bridge, in a single period went from single digits to almost 300 unique clients. Is this normal/possible or what other explanation could there be.

4 3

Bridge Location matter?
by Astroskis Lists 13 Feb '21

13 Feb '21

Hello, Does the physical location matter for a Bridge? For example if I'm able to put it in a unusual geographical place would that benefit the network? I'm asking because I believe when you request a bridge it does not take location into account so would it matter? Thank you

3 3

ulyssa
by Anonforpeace 12 Feb '21

12 Feb '21

Hello: Does anyone know what repo I need to install for Linux Mint Ulyssa 20.1? Trying to update my bridge and can't find this repo. Thanks

2 1

Re: [tor-relays] 'reserved' bridge distribution mechanism average time until use
by Robert Bloch 11 Feb '21

11 Feb '21

How long does it take for a bridge with 'reserved' bridge distribution to see its first user? On average.

1 0

cannot update respository
by Anonforpeace 10 Feb '21

10 Feb '21

Hello: I hope you can help. My bridge is offline because: Please upgrade! This version of Tor (0.4.2.7) is not recommended, according to the directory authorities. Recommended versions are: 0.3.5.10,0.3.5.11,0.3.5.12,0.3.5.13,0.4.3.3-alpha,0.4.3.4-rc,0.4.3.5,0.4.3.6,0.4.3.7,0.4.3.8,0.4.4.1-alpha,0.4.4.2-alpha,0.4.4.3-alpha,0.4.4.4-rc,0.4.4.5,0.4.4.6,0.4.4.7,0.4.5.1-alpha,0.4.5.2-alpha,0.4.5.3-rc,0.4.5.4-rc,0.4.5.5-rc,0.4.5.6 When I try to update it I get this: darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ lsb_release -c Codename: ulyssa darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ cd /etc/apt/sources.list bash: cd: /etc/apt/sources.list: Not a directory darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ cd /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ ls official-package-repositories.list tor-project.list darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ lsb_release -c Codename: ulyssa darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E8… | gpg --import gpg: key EE8CBC9E886DDD89: 83 signatures not checked due to missing keys gpg: error writing keyring '/home/darkhoodie/.gnupg/pubring.kbx': Permission denied gpg: error reading '[stdin]': Permission denied gpg: import from '[stdin]' failed: Permission denied gpg: Total number processed: 0 darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E8… | gpg --import gpg: key EE8CBC9E886DDD89: 83 signatures not checked due to missing keys gpg: error writing keyring '/home/darkhoodie/.gnupg/pubring.kbx': Permission denied gpg: error reading '[stdin]': Permission denied gpg: import from '[stdin]' failed: Permission denied gpg: Total number processed: 0 darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - gpg: directory '/root/.gnupg' created gpg: keybox '/root/.gnupg/pubring.kbx' created gpg: WARNING: nothing exported E: This command can only be used by root. darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo apt update Ign:1 http://packages.linuxmint.com ulyssa InRelease Hit:2 http://packages.linuxmint.com ulyssa Release Hit:3 http://archive.canonical.com/ubuntu focal InRelease Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:6 http://archive.ubuntu.com/ubuntu focal InRelease Hit:7 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease Ign:9 https://deb.torproject.org/torproject.org ulyssa InRelease Err:10 https://deb.torproject.org/torproject.org ulyssa Release 404 Not Found [IP: 95.216.163.36 443] Reading package lists... Done N: Ignoring file 'sources.list.d' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The repository 'https://deb.torproject.org/torproject.org ulyssa Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ Not sure where I'm going wrong. Please help. Thank you

2 1

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

10 Feb '21

> Hello Patrice > > would be great if you can share your script , thanks. Hi, sure, with pleasure. But I have to say I am not a professional programmer. There are surely better ways to do this, but it works for me. Before you can use it you have to make it executable with this command: chmod +x build_tor_from_source.sh And make sure to read the info in the script. After that you are ready to roll. regards Patrice ## build_tor_from_source.sh ######################################################################## ####################################################### ## This script is for a automatic installation of tor out of the sources. ## What it will do: # # 1. It downloads the newest tarball, compiles and installs it. # 2. It copies the data dir (with the keys) and the torrc. # 3. It removes all installations files. # 4. It starts tor as the current user # 5. It adds tor as crontab (@bootup) of current user # 6. changes the permissions of the tor logs, tor folder and torrc for the current user # 6. At the end it shows the logs to check the tor startup process ## What are the requirements for this installation script # # - the torrc must be in the same folder as this script # - check the paths used in this script if they fit for your system (the default paths are for Pi OS) # - this script must be in a location where it has write permisssions (for example home folder of current user) ## What this script can't do # # Tor is not compiled wioth systemd support, so this won't work until you switch it on. ####################################################### #! /bin/bash # echo output colour # green="tput setaf 2" white="tput setaf 7" yellow="tput setaf 3" red="tput setaf 1" ##################### $yellow echo -e "\n\n####################" echo -e "# Tor Installation #" echo -e "####################\n" # show tor version for comparison $yellow echo -e "\nTor version on the system ->" $green tor --version | cut -b 13-20 echo # new line $yellow echo -e "Tor version online available ->" $green lynx -nonumbers -dump https://dist.torproject.org | grep "https://dist.torproject.org/tor-" | grep -v "alpha" | grep -v "rc" | grep -v "asc" | tail -1 | cut -b 33-40 # question for installation $red echo -e "\n\n" read -p "Installing new version? [y/n]: " -n 1 -r echo if [[ $REPLY =~ ^[Yy]$ ]] then $green echo -e "\nstopping tor on system...\n" $white sudo killall tor $green echo -e "\ndone.\n" $green echo -e "\nsystem update and installing needed packages...\n" $white sudo apt update sudo apt upgrade -y sudo apt install -y libevent-dev libssl-dev zlib1g-dev asciidoc lynx $green echo -e "\ndone.\n" $white build_dir="temp" mkdir $build_dir cd $build_dir # in ./temp $green echo -e "\ndownloading tor from git repo...\n" $white lynx -nonumbers -dump https://dist.torproject.org | grep "https://dist.torproject.org/tor-" | grep -v "alpha" | grep -v "rc" | grep -v "asc" | tail -1 | xargs wget tar -xvf tor*.tar.gz cd `ls -d */` # in ./temp/tor-* $green echo -e "\ndone.\n" $green echo -e "\nbacking up data dir, and changing its user..." $white sudo cp -arv /var/lib/tor ./tor sudo chown -R $(whoami) ./tor $green echo -e "\ndone.\n" $green echo -e "\ncompiling, removing old version, installing new version...\n" $white ./configure && make && sudo make uninstall && sudo make install $green echo -e "\ndone.\n" $green echo -e "\ncopying torrc and restoring data directory...\n" $white sudo cp -av ../../torrc /usr/local/etc/tor/torrc sudo chwon $(whoami):root /usr/local/etc/tor/torrc sudo cp -arv ./tor /var/lib/tor $green echo -e "\ndone.\n" cd .. # in ./temp cd .. # in ./ $green echo -e "\nremoving build folder and system files...\n" $white sudo rm -R $build_dir sudo apt autoclean sudo apt autoremove $green echo -e "\ndone.\n" $green echo -e "\nadding tor as crontab to start tor on boot...\n" $white if sudo grep -q "@reboot /usr/local/bin/tor --quiet" /var/spool/cron/crontabs/$(whoami) then echo -e "tor is already present as crontab" else #echo -e "@reboot /usr/local/bin/tor --quiet" | sudo tee -a /var/spool/cron/crontabs/$(whoami) echo -e "tor is added as crontab" fi $green echo -e "\ndone.\n" $green echo -e "\nchanging user of log files...\n" $white sudo chown -R $(whoami) /var/log/tor $green echo -e "\ndone.\n" $green echo -e "\nstarting tor...\n" $white # start tor /usr/local/bin/tor --quiet echo # new line $yellow echo -e "\ntor log\n" $white sudo tail -c+1 -f /var/log/tor/notices.log else $white exit 1 fi ########################################################################

1 0

tor on Ubuntu Server 20.04.2 LTS
by tor 10 Feb '21

10 Feb '21

Hi All, Which version of tor runs on Ubuntu Server 20.04.2 LTS 64bit, if any? Thanks matt

1 0

Re: [tor-relays] Tor relay failed to start after upgrade (0.4.4.6 --> 0.4.5.5) [solved]
by David Goulet 09 Feb '21

09 Feb '21

On 09 Feb (11:55:12), tschador(a)posteo.de wrote: > Tonight my Tor relay on Raspberry Pi (buster) was upgraded from > 0.4.4.6-1~bpo10+1 to 0.4.5.5-rc-1~bpo10+1 automaticly, but failed to start: > > --- > [notice] Opening OR listener on 0.0.0.0:587 > [notice] Opened OR listener connection (ready) on 0.0.0.0:587 > [notice] Opening OR listener on [::]:587 > [warn] Socket creation failed: Address family not supported by protocol > [notice] Opening Directory listener on 0.0.0.0:995 > [notice] Closing partially-constructed OR listener connection (ready) on > 0.0.0.0:587 > [notice] Closing partially-constructed Directory listener connection (ready) > on 0.0.0.0:995 > --- > > Until then there was no change in my torrc: > > ORPort 587 > DIRPORT 995 Oh wow, interesting, so your Pi doesn't support IPv6 for some reasons and it failed to start with this config. I have opened: https://gitlab.torproject.org/tpo/core/tor/-/issues/40283 In 0.4.5.x tor, things have changed where tor will try to auto discover an IPv6 and automatically bind to it if only "ORPort <PORT>" is used. In other words, it now binds to 0.0.0.0 and [::] by default. It then publish any discovered _usable_ and _reachable_ IPv4/IPv6. If it doesn't find any IPv6, it will still listen but won't publish any IPv6. > > It seems the value [address:] is no longer optional if you're not IPv6 ready > [1]: > > ORPort [address:]PORT|auto [flags] > DirPort [address:]PORT|auto [flags] > > So I have to change my torrc to: > > ORPort 0.0.0.0:587 > DIRPORT 0.0.0.0:995 Another option would have been to add the "IPv4Only" flag to the ORPort line and should have done it for you. Cheers! David -- YrY9JHvSOJpDfyKS5AyL8h/BjZ/SQEkh00q9ek+1BXk=

1 0

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 04 Feb '21

04 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

Re: [tor-relays] tor-relays Digest, Vol 120, Issue 25
by Patrice Bönig 03 Feb '21

03 Feb '21

Am 03.02.2021 um 21:14 schrieb Patrice Bönig: > I am now compiling the new 0.4.4.7 version and by that I saw that the > entry of "systemd support (--enable-systemd)" is is "no". So I assume > that the systemd functionality is not on board, or am I wrong? > How do I enable for the compiling process? > > regards > Karl > > >> Permissions issue of /var/lib/tor / DataDirectory most likely, and >> Tor can't fix it itself since it's likely owned by root, however the >> systemd unit starts it under a separate user. 2021-01-22 12:03 GMT, >> Patrice B?nig <mailinglist(a)pboenig.de>: >>> Hi @ list, >>> >>> I am operating a relay for several years and I really do like it and >>> will do it for more years. >>> >>> My current relay residents on Pi 4. At first I installed it via apt but >>> now the 32 Bit sources are no longer available. So I thought I could >>> build the from source. >>> >>> The building process went well but now I have a problem with the user >>> permissions. I can't get tor really running. >>> >>> _My first attempt was:_ >>> >>> To start tor with "systemctl start tor". But tor won't start and " >>> journalctl -u tor" says only this: >>> >>> Jan 22 09:06:23 rpi4tor systemd[1]: Starting LSB: Starts The Onion >>> Router daemon >>> Jan 22 09:06:23 rpi4tor systemd[1]: Started LSB: Starts The Onion Router >>> daemon >>> Jan 22 09:08:32 rpi4tor systemd[1]: Stopping LSB: Starts The Onion >>> Router daemon >>> Jan 22 09:08:32 rpi4tor systemd[1]: tor.service: Succeeded. >>> Jan 22 09:08:32 rpi4tor systemd[1]: Stopped LSB: Starts The Onion Router >>> daemon >>> lines 1-6/6 (END)...skipping... >>> -- Logs begin at Thu 2019-02-14 11:11:59 CET, end at Fri 2021-01-22 >>> 11:54:47 CET. -- >>> Jan 22 09:06:23 rpi4tor systemd[1]: Starting LSB: Starts The Onion >>> Router daemon processes... >>> Jan 22 09:06:23 rpi4tor systemd[1]: Started LSB: Starts The Onion Router >>> daemon processes. >>> Jan 22 09:08:32 rpi4tor systemd[1]: Stopping LSB: Starts The Onion >>> Router daemon processes... >>> Jan 22 09:08:32 rpi4tor systemd[1]: tor.service: Succeeded. >>> Jan 22 09:08:32 rpi4tor systemd[1]: Stopped LSB: Starts The Onion Router >>> daemon processes. >>> >>> _My second attempt was:_ >>> >>> I changed the user of all tor files to the current user "pi". After that >>> I was able to start tor with "tor --quiet" as user "pi". All went fine >>> until I rebooted the system and all my changes to "pi" where changed to >>> "debian-tor". >>> >>> _My third attempt was:_ >>> >>> I did "sudo tor --quiet". It works, but in "notices.log" is the >>> information that I shouldn't do that. >>> >>> >>> So, now I am standing here and don't know what to do. I would like to >>> start tor via systemd but I don't know what's wrong (maybe the >>> permissions). Does someone has a hint for me? >>> >>> regards, >>> Karl >>> >>> >>>

1 0