- tor-relays - lists.torproject.org

New Test for Measuring the Accuracy of Tor Relays' Advertised Bandwidths
by Georg Koppen 07 Jun '21

07 Jun '21

Hello everyone! Some of you might remember the speed test Rob had been running during August 2019 to investigate the accuracy of the advertised bandwidth a relay is reporting in its server descriptor.[1] Back then this involved, for each relay, downloading several large data streams for a period of about 20 seconds to get a better estimation of the relay's true capacity (See: [1] and follow-up emails for the exact details of the experiment). We plan to do this speed test again in about 1 week and relay operators can opt-out of it (again) if they want to. We still believe that the overhead of this speed test is in line with regular usage, but if anyone doesn't want to participate that's fine. Let us know if so (by replying to this thread or off-list, if preferred) and we remove your relay(s) from the list to scan. Thanks, Georg [1] https://lists.torproject.org/pipermail/tor-relays/2019-July/017535.htmlff.

4 5

current HSDir flag requirements
by Scott Bennett 03 Jun '21

03 Jun '21

What are all the current requirements for a relay to get a HSDir flag? 96 (97?) hours of uptime and what else? Can someone tell me what my relay, MYCROFTsOtherChild, is missing for a HSDir flag? 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 * **********************************************************************

4 9

Block certain .onion websites
by Tor Operator 29 May '21

29 May '21

Hello, exit node operator here. I share the values of the TOR foundation, that’s why I’m operating an exit node but I can’t unsee all the bad it is used for. I know it would sound like censorship but wouldn’t it be possible for an exit relay to block certain (mainly cp) .onion websites so that they cannot be visited from certain exit nodes? Thanks in advance

3 2

ssh request from Virgin Media (Liberty Global)
by Cristiano Kubiaki Gomes 27 May '21

27 May '21

I have a Relay and a Bridge up and running with ssh password disabled, ssh port changed and fail2ban installed. With that I noticed that one particular IP was trying to ssh my both machines and that IP belongs to Liberty Global, an Anglo-Dutch-American telecommunication company which is owner of the Virgin Media, UPS and Vodafone. I was wondering, why is this company trying to ssh my Tor machines? Has anyone else noticed this? I am afraid to share the company IP here because they could be here on this list and they could use one IP to target on specific subject and if I disclose that IP they could find me out 😂 It’s just a FYI. Stay safe. -- Cristiano Kubiaki Telegram <https://telegram.me/cris_kubiaki> | LinkedIn <https://www.linkedin.com/in/cristianokubiaki/> | Twitter <https://twitter.com/criskubiaki> ITIL - MCP - MCDST - MCTS - DCSE

4 3

Wrote a small "script" for automatic family synchronisation
by charles＠torrelays.ru 25 May '21

25 May '21

Hey y'all. I made a small script to automate the Family setup of relays and wanted to get your opinion on it. step 1) create a file called sync_Fam.sh in the /home/ directory. (or wherever you feel like creating it) the file should contain this: sed -i '/MyFamily/d' /etc/tor/torrc cat "FamilyList.txt" >> /etc/tor/torrc What this will do is remove the line with "MyFamily" in the torrc file, and add the contents of a file called "FamilyList.txt" to the torrc file. FamilyList.txt will, ofcourse, contain the line MyFamily $fingerprint1, $fingerprint2, $fingerprint 3,.... step 2) create a webserver where you display the list of fingerprints to add I used nginx for this, use whatever you feel like using. as long as it works :p step 3) search for the location of the .pid file of tor. if you want to use a custom location you can do it by adding the line "PidFile {locationofwhereyouwanttoplaceit}" i decided to also place it in the home directory. step 4) add a crontab (you can use crontab -e) 45 * * * * cd /home/ && wget -N http://{IPofTheWebServer}/FamilyList.txt 46 * * * * cd /home/ && ./sync_Fam.sh 47 * * * * kill -HUP $(cat /home/tor.pid) what this will do, is download the FamilyList.txt file from the webserver, run sync_Fam.sh, and reload tor. (-HUP sends a reload signal) so.. what do y'all think of it? is it a good script?

1 0

Re: [tor-relays] TOR installation (walentyczerwinski85)
by Patrice Bönig 23 May '21

23 May '21

Hi, sure, I wrote a script for this. I always compile Tor to use it as a relay on a Raspberry Pi. I have attached the script. regards, Patrice ###### # Script # ###### ############################################################################################################## ## 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" # lynx installation sudo apt install -y lynx # 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 $green echo -e "\ndone.\n" $white build_dir="temp" mkdir $build_dir cd $build_dir # in ./temp $green echo -e "\ndownloading tor from https://dist.torproject.org ...\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 installation 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 it on @reboot...\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

Help with running a Tor Bridge
by Cor.ling 22 May '21

22 May '21

Hi, I have set up a bridge on Kubuntu following this guide: https://community.torproject.org/relay/setup/bridge/debian-ubuntu/ In TODO1 I put: 443 and in TODO2: 80 (I used these values only because they were in the example). But in my log (/var/log/syslog) I'm seeing these errors: Tor[X]: Your server has not managed to confirm reachability for its ORPort(s) at X.X.X.X:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Tor[X]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3600 seconds] How can I resolve them? And also: how can I enable IPv6?

3 2

TOR installation
by walentyczerwinski85 20 May '21

20 May '21

Hi, guys. I'm going to compile TOR on Ubuntu 20 server. Can you tell me which packages (dependencies) do I have to install before compilation? Which OS settings would you recommend to change before launching a relay?

1 0

Documenting rejection of bad relays
by Georg Koppen 17 May '21

17 May '21

Hello! We finally sat down and documented the current criteria for and the process of dealing with bad relays. If you are interested in that topic, have a look at our wiki page[1] which is explaining the details. We plan to keep that page updated as our criteria and process are evolving in the future. Feedback is much appreciated! Georg [1] https://gitlab.torproject.org/tpo/network-health/team/-/wikis/Criteria-for-…

1 0

let's make ContactInfo mandatory for exits (and warn others)
by nusenu 14 May '21

14 May '21

After looking at lots of malicious relay data of the past few months I've come to the conclusion that exit relays without ContactInfo are largely run by malicious actors. I propose to make torrc's ContactInfo mandatory for exit relays with the following timeline: * tor 0.4.6: log a warning that tor will require ContactInfo to be set on an exit relays starting with tor v0.4.7 * tor 0.4.7: no longer assign the exit flag to relays not having a ContactInfo (< 5 chars) in their descriptor. Log a warning for relay operators, I'll add graphs that show exit fraction provided by exit relays without ContactInfo over time to OrNetStats. Is this an effective remedy to deter malicious actors? No and it is not meant to be one. It is trivial to set a random non-empty ContactInfo, only in combination with other countermeasures it becomes actually useful. ContactInfo is also mentioned in this draft: https://gitlab.torproject.org/tpo/community/team/-/wikis/Expectations-for-R… I'll make it easy for Tor Browser users to exclude exit relays without ContactInfo from their configuration. This might makes the proposal irrelevant should the release alone result in exits getting non-empty ContactInfos. More details will follow soon. kind regards, nusenu -- https://nusenu.github.io

8 13