- tor-relays - lists.torproject.org

Verify my Relay
by S1l3nt Hash 25 Jun '21

25 Jun '21

Hello, I wanted to do my part in helping the TOR network grow, so I've started a tor relay on a debian system. After running for a while and monitoring on Nyx, and checking Relay Search I've notice my link says "Offline". Just wanted to know if there is a way to confirm working status, apologies in advance as I'm quite new to this. Torrc Nickname **** SocksPort 0 RunAsDaemon 1 Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip) ContactInfo (my email) Log notice file /var/log/tor/notices.log ExitPolicy reject6 *:*, reject *:* RelayBandwidthRate 16777216 RelayBandwidthBurst 16777216 DisableDebuggerAttachment 0 ControlPort 9051 CookieAuthentication 1 CookieAuthFile /var/lib/tor/control_auth_cookie CookieAuthFileGroupReadable 1 DataDirectoryGroupReadable 1 HashedControlPassword *** Also configured Port Forwarding on my router for 9001 and 9030 to the private IPv4 address on the tor relay. Confirmed with my ISP no ports are being blocked. When I first started I had the confirmation MSG that DirPort could be reached, and have active incoming and outing connections. Now currently only have several outgoing connections. Was at one stage appearing "Online" on Relay Search, now "Offline" Currently have: [NOTICE] No circuits are opened. Relaxed timeout for circuit *** (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 7740 seconds] Have not configured 9001 and 9030 to open in linux, are they by default? Thanks in advance for any help and knowledge, looking forward to helping. Hash.

4 3

Bad relay mark
by Zakwan Kalb 24 Jun '21

24 Jun '21

Please email me (kalbzakwan(a)gmail.com) if your relay was marked as bad relay. There is something suspicious happening, I would like to discuss it.

1 0

Torweather is still alive or back ;-)
by lists＠for-privacy.net 22 Jun '21

22 Jun '21

Damn cool, I was surprised when I got mail from torweather.org. (Some IPv6 addresses were down and I didn't notice.) And you can adjust your delivery frequency. Relay down since 3, 12, 24, 48 Hours or 1 Week. https://github.com/thingless/torweather Hint: You must have a working mail address in torrc contact info for it. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

1 0

tor fails on start-up after yum update
by Eddie 21 Jun '21

21 Jun '21

Running a CentOS 7.9 system, pulling tor updates from https://rpm.torproject.org/centos/$releasever/$basearch The last 2 times that tor has been yum updated, the restart of the service has just stopped, at exactly the same point: Jun 18 06:46:50.000 [notice] Tor 0.4.6.5 opening log file. Jun 18 06:46:50.830 [notice] We compiled with OpenSSL 100020bf: OpenSSL 1.0.2k 26 Jan 2017 and we are running with OpenSSL 100020bf: 1.0.2k-fips. These two versions should be binary compatible. Jun 18 06:46:50.831 [notice] Tor 0.4.6.5 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma 5.2.2, Libzstd 1.5.0 and Glibc 2.17 as libc. Jun 18 06:46:50.831 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jun 18 06:46:50.831 [notice] Read configuration file "/usr/share/tor/defaults-torrc". Jun 18 06:46:50.831 [notice] Read configuration file "/etc/tor/torrc". Jun 18 06:46:50.833 [notice] Based on detected system memory, MaxMemInQueues is set to 6342 MB. You can override this by setting MaxMemInQueues by hand. Jun 18 06:46:50.833 [notice] You configured a non-loopback address '192.168.0.254:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Jun 18 06:46:50.833 [notice] Opening Socks listener on 192.168.0.254:9100 Jun 18 06:46:50.833 [notice] Opened Socks listener connection (ready) on 192.168.0.254:9100 Jun 18 06:46:50.833 [notice] Opening Control listener on 127.0.0.1:9051 Jun 18 06:46:50.833 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051 Jun 18 06:46:50.833 [notice] Opening OR listener on 0.0.0.0:9001 Jun 18 06:46:50.834 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001 Jun 18 06:46:50.834 [notice] Opening Directory listener on 0.0.0.0:9030 Jun 18 06:46:50.834 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030 Jun 18 06:46:51.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Starting the service then it starts correctly. I also couldn't see anything out of the ordinary in the main system logs, other than it echoing the above. Any ideas on what's going on here. Also, what is the correct setting for systemctl enable/disable tor/tor-master (I don't have any tor@ services), because I get inconsistent results using tor-master. Issuing "systemctl stop tor-master" will stop the accompanying tor instance, but "systemctl start tor-master" doesn't start it, but a "systemctl restart tor-master" does do a stop/start. I haven't had time to experiment with what happens on a re-boot (yet). Cheers.

2 1

Can't compile 0.4.6.5 on Ubuntu 18.04
by William Denton 16 Jun '21

16 Jun '21

I went to upgrade a relay running on Ubuntu 18.04 to the new release (0.4.6.5) and to my surprise it didn't compile. Every other version has built without any trouble. Wading into the Gitlab site was rather confusing, so I thought I'd send this here, in the hopes it reaches the right people and someone else might be interested. I ran ./configure, then make, and pretty soon this happened: CC src/feature/dirclient/dirclient.o In file included from ./src/core/or/or.h:50:0, from src/feature/dirclient/dirclient.c:13: src/feature/dirclient/dirclient.c: In function ‘dir_client_decompress_response_body’: ./src/lib/log/ratelim.h:55:27: error: initializer element is not constant #define RATELIM_INIT(r) { (r), 0, 0, 0 } ^ src/feature/dirclient/dirclient.c:1877:38: note: in expansion of macro ‘RATELIM_INIT’ static ratelim_t warning_limit = RATELIM_INIT(LOG_INTERVAL); ^~~~~~~~~~~~ ./src/lib/log/ratelim.h:55:27: note: (near initialization for ‘warning_limit.rate’) #define RATELIM_INIT(r) { (r), 0, 0, 0 } ^ src/feature/dirclient/dirclient.c:1877:38: note: in expansion of macro ‘RATELIM_INIT’ static ratelim_t warning_limit = RATELIM_INIT(LOG_INTERVAL); ^~~~~~~~~~~~ Makefile:12141: recipe for target 'src/feature/dirclient/dirclient.o' failed make[1]: *** [src/feature/dirclient/dirclient.o] Error 1 make[1]: Leaving directory '/usr/local/src/tor/tor-0.4.6.5' Thanks, Bill -- William Denton https://www.miskatonic.org/ Librarian, artist and licensed private investigator.

3 3

tor relay + sslh
by Casper 14 Jun '21

14 Jun '21

Hello, I recently discovered an SSL multiplexer called "sslh": """ sslh accepts connections on specified ports, and forwards them further based on tests performed on the first data packet sent by the remote client. Probes for HTTP, SSL, SSH, OpenVPN, tinc, XMPP are implemented, and any other protocol that can be tested using a regular expression, can be recognized. A typical use case is to allow serving several services on port 443 (e.g. to connect to ssh from inside a corporate firewall, which almost never block port 443) while still serving HTTPS on that port. Hence sslh acts as a protocol multiplexer, or a switchboard. Its name comes from its original function to serve SSH and HTTPS on the same port. """ Since many of my network services claims to listen on 433 (to bypass mobile network limitations), I'm thinking to configure and deploy sslh on large scale. If tor handshake can be handled by sslh, could the process (of the tor relay) be listening on 127.0.0.1:12345 and publish good relay descriptor as well ? Currently, in my relay config, I have the following: """ ORPort 26719 ORPort [{{ ansible_default_ipv6.address }}]:26719 DirPort 26720 and Address <my_public_ipv4_here> """ Tor will accept to be listening on the localhost interface only? """ ORPort 127.0.0.1:26719 Address <my_public_ipv4_here> """ Best regards, -- GnuPG: AE157E0B29F0BEF2 at keys.openpgp.org CA Cert: https://dl.casperlefantom.net/pub/ssl/root.der

3 2

Problem moving my Tor Bridge Relay
by Cor.ling 13 Jun '21

13 Jun '21

Hello, I have a Tor Bridge and it worked well (thanks also for your kind support) but it doesn't work anymore after I tried to move it. Basically I copied the 'Keys' folder (at /var/lib/tor/keys) on a USB flash drive. After that I put the folder into the /var/lib/tor folder of the new device (deleting the pre-existing "Keys" folder). But I receive these errors on syslog (/var/log/syslog): > "Jun 12 15:13:59 PC systemd[1]: Stopped Anonymizing overlay network for TCP. > Jun 12 15:13:59 PC systemd[1]: Starting Anonymizing overlay network for TCP... > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.472 [notice] Tor 0.4.5.6 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1j, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.33 as libc. > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.472 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.472 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.472 [notice] Read configuration file "/etc/tor/torrc". > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.474 [notice] Based on detected system memory, MaxMemInQueues is set to 2875 MB. You can override this by setting MaxMemInQueues by hand. > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.476 [warn] /var/lib/tor/keys is not owned by this user (debian-tor, 124) but by root (0). Perhaps you are running Tor as the wrong user? > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.476 [warn] Failed to parse/validate config: Couldn't access private data directory "/var/lib/tor/keys" > Jun 12 15:13:59 PC tor[38309]: Jun 12 15:13:59.476 [err] Reading config failed--see warnings above. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Control process exited, code=exited, status=1/FAILURE > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Failed with result 'exit-code'. > Jun 12 15:13:59 PC systemd[1]: Failed to start Anonymizing overlay network for TCP. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Scheduled restart job, restart counter is at 4. > Jun 12 15:13:59 PC systemd[1]: Stopped Anonymizing overlay network for TCP. > Jun 12 15:13:59 PC systemd[1]: Starting Anonymizing overlay network for TCP... > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.721 [notice] Tor 0.4.5.6 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1j, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.33 as libc. > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.721 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.721 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.721 [notice] Read configuration file "/etc/tor/torrc". > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.723 [notice] Based on detected system memory, MaxMemInQueues is set to 2875 MB. You can override this by setting MaxMemInQueues by hand. > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.726 [warn] /var/lib/tor/keys is not owned by this user (debian-tor, 124) but by root (0). Perhaps you are running Tor as the wrong user? > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.726 [warn] Failed to parse/validate config: Couldn't access private data directory "/var/lib/tor/keys" > Jun 12 15:13:59 PC tor[38314]: Jun 12 15:13:59.726 [err] Reading config failed--see warnings above. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Control process exited, code=exited, status=1/FAILURE > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Failed with result 'exit-code'. > Jun 12 15:13:59 PC systemd[1]: Failed to start Anonymizing overlay network for TCP. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Scheduled restart job, restart counter is at 5. > Jun 12 15:13:59 PC systemd[1]: Stopped Anonymizing overlay network for TCP. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Start request repeated too quickly. > Jun 12 15:13:59 PC systemd[1]: tor(a)default.service: Failed with result 'exit-code'. > Jun 12 15:13:59 PC systemd[1]: Failed to start Anonymizing overlay network for TCP." (i'm using a PC with Kubuntu 21.04 and I followed this guide for the setting up: https://community.torproject.org/relay/setup/bridge/debian-ubuntu/) What can I do to solve these errors?

2 1

torrc
by Walenty Czerwinski 12 Jun '21

12 Jun '21

I wonder what's the difference between BandwidthRate, MaxAdvertisedBandwidth and RelayBandwidthRate?

1 0

Running Tor exit nodes on university networks
by Andreas Kempe 12 Jun '21

12 Jun '21

Hello everyone, I'm a member of Lysator ACS at Linköping university, Sweden. I'm currently investigating the possibility for our computer society to run Tor exit nodes. The IT department has made it clear that they will need some convincing that this is a good idea. One thing that they are wondering is whether there are other universites with experience running Tor nodes. If anyone is currently running Tor nodes on university networks, I'd love to hear about your experiences. A few questions that turned up are listed below. - Have you seen any good or bad press because of the node? - Are you receiving a lot of abuse complaints? - How are you handling abuse complaints? - How are you protecting the rest of your infrastructure from possibly malicious traffic? - Do you have any killer arguments as to why supporting Tor is a good idea that helped sway the people in charge at your university? Thank you in advance for any feedback! Cordially, Andreas Kempe

4 5

G-Core Labs and their humanoid robots
by Tor Relays 11 Jun '21

11 Jun '21

TL;DR: G-Core Labs does not understand their abuse detection software and their support agents are a bunch of humanoid robots. Dear customer, Due to suspicious activity SMTP ports have been blocked. Affected service ID: <id>. Destination port: 25, 465, 587. To unblock contact support. Me: hello, i guess you are referring to a recent spamhaus entry? i do not use ports 25, 465, 587 so it likely is a false positive. I don't need these ports open but i would prefer if you could unlock them in case i would like to use them in the future. otherwise i might wonder why they don't work without remembering that they got blocked on your end. Thanls Support agent 1: Hello, In terms of Acceptable Use Policy (AUP), clause 2(d), we reserve a right to block SMTP ports if your service is not located at our platform. Please, find the list of blockage cases and solutions. 1) Service belongs to third parties. Unfortunately, we have to deny your request of unblocking SMTP ports according to AUP. 2) Service belongs to our platform. Please, specify domain you send emails to. If domain is fine, we'll unblock ports accordingly. 3) You didn't send any emails. Please, check your server to find the reason of spamming. As soon you resolve the issue, we'll unblock ports. However if our automated system identifies spamming on your server again, we'll have to block SMTP ports permanently. We kindly ask you to send a reply in a detailed manner so we could analyze your case accordingly. Me: I will repeat myself: I do not send emails. Please unblock the SMTP ports or specify why you blocked the SMTP ports. Thanks. Support agent 1: Check your network settings, perhaps something could cause it. Tell us what you will found and we will figure it out. Me: I do not have a reason to believe the server got hacked and i do not use the server to send emails so it likely is a false positive. Why were the SMTP ports blocked? Support agent 1: It was blocked because automatic monitoring system find your activity suspicious. Now, trust level of your traffic for IP has been increased however the traffic is still automatically monitored. If the system of automatization identifies your traffic as illegitimate or if we receive an infringement report, we'll have to disable ports once again. Me: Please do not block any ports without my consent when you do not have any logfiles that prove any misbehavior. "Automatic monitoring system find your activity suspicious" does not help in debugging any possible misbehavior coming from my server. Do you have information about where i can read up about the function of your automatic monitoring system to prevent this problem? Support agent 1: We can't share information about algorithm. Four days later, different support agent: Dear customer, Due to suspicious activity SMTP ports have been blocked. Affected service ID: <id>. Destination port: 25, 465, 587. To unblock contact support. Me: hello, can you please give me more details about the suspicious activity? Support agent 1: Hello, In terms of Acceptable Use Policy (AUP), clause 2(d), we reserve a right to block SMTP ports if your service is not located at our platform. Please, find the list of blockage cases and solutions. 1) Service belongs to third parties. Unfortunately, we have to deny your request of unblocking SMTP ports according to AUP. 2) Service belongs to our platform. Please, specify domain you send emails to. If domain is fine, we'll unblock ports accordingly. 3) You didn't send any emails. Please, check your server to find the reason of spamming. As soon you resolve the issue, we'll unblock ports. However if our automated system identifies spamming on your server again, we'll have to block SMTP ports permanently. We kindly ask you to send a reply in a detailed manner so we could analyze your case accordingly. Me: Thanks but i know the AUP. The server does not send any emails and i do not have a reason to believe the server got hacked so please tell me the timestamp and destination of the connection that triggered your automatic monitoring system. Support agent 1: Let us please discuss your issue with our colleagues. We will inform you on this ticket. Support agent 1: Hello! Thank you for waiting! Unfortunately, we have to decline your unblocking request. As we see there is a second block on the same server. We couldn't unblock ports if they were blocked once Me: My question was: What triggered the block? Support agent 1: We couldn't provide you detailed information about SMTP-blocking system, sorry. The block is triggered if your server has suspicious activity on SMTP ports. Me: i understood that. What does "suspicious activity" means? Support agent 1: Let us, please, clarify this information with our engineers Me: Thank you. I hope you understand that it's an unfortunate situation when i do not find any misbehavior on the server but your "automatic monitoring system" accuses me of misbehavior and the answer is "there was suspicious activity". I am awaiting the response. Support agent 1: We have received a reply from your colleagues. Sorry, but we couldn't announce how this technology works. It is confidential information! Me: Can you forward me to someone higher or is there an address where i can complain? Support agent 2: Hello, Let us please discuss this moment with colleagues. Please stay tuned! Support agent 3: Thank you for waiting. Unfortunately, we can't forward somebody higher to you or give you an email additional email address. All communications take place via the support team. If you want to complain, please send us your complaint and we will send it to our colleagues. Me: Hello <name>! Sure, i can summarize it for you: I would like to complain about a malfunction in your "automatic monitoring system". Four days ago i received a ticket that SMTP ports are blocked due to "suspicious activity". I answered the support agent that the server is not used for sending emails and there is no sign of a malfunction on the server so it very likely is a false positive and he unblocked the SMTP ports. Today i received such a ticket again and the server is still not used for sending emails and there still is no sign of malfunction. To help you understand the incident i would need some information from you: - the source/destination IP and port that triggered the automatic monitoring system - an exact timestamp What solution can you offer me? Support agent 3: I'll send your message to our colleagues and let you know about the result. Support agent 3: Unfortunately, we can't provide you with any information that you've been asking for and we have to decline your request for unblocking. Our decision is based on our Master Service Agreement. You can find it here: https://gcorelabs.com/legal/ Me: What is the reason that you can not provide me with the requested information? Support agent 3: We don't provide that kind of information. As we already said it's confidential information. Me: Punishing the user for something, then making the information about the cause of the punishment as confidental for him is interesting. Are you sure that you properly understand the function of your "automatic monitoring service" and what steps will you take to prevent false positive results in the future? Support agent 3: Our engineers are working to improve the technology of SMTP ports blocking, but I'm afraid I can't share with you any additional information about it. I gave up after that. This happens when you use A/I to detect abuse and degrade humans to communicate A/I decisions. A/I will abuse us all.

5 6

Exit
by Walenty Czerwinski 11 Jun '21

11 Jun '21

Is there a chance to get problems with law enforcement in Poland because of operating exit relays? I heard in some countries law enforcement arrested relay operators thinking they committed a crime with a server where relays are hosted.

2 1

IPv6 not showing up on tor exit node
by pimpnet 10 Jun '21

10 Jun '21

I run a tor exit node and have properly configured IPv6 but sometimes it does not appear on the tor relay list. This is fixed when I reboot the tor service but what could be the reason?

1 0

More Tor measurements next week [opt out]
by Zachary Newman 08 Jun '21

08 Jun '21

tl;dr: Low-load measurements coming; no action needed unless you would like to opt out. Hi all, Next week (week of 2021-05-31), we will be starting a wide-scale measurement of the latencies between relays on the Tor network for a research project; these measurements will last an estimated 1-2 months. We have the permission of the Tor Research Safety Board and this information will ultimately be used to improve the network. Further, the load at any one time on the Tor network from these measurements will be limited and negligible (approximately the same load as the start-up tests of a few new Tor clients). We are coordinating with the currently-running speed test[1], and will start our measurements after the conclusion of this speed test. If you operate a relay and would like to opt out of these measurements, please send us an email (shortor(a)csail.mit.edu) including the fingerprint of your relay(s). We will stop sending you traffic and, if the test has begun, delete past measurements involving your relay(s). Status updates will be posted publicly[2], and we will bump this thread before we start and if anything important changes. Please contact shortor(a)csail.mit.edu with any questions. Regards, Zack Newman (on behalf of the ShorTor team) [1] https://lists.torproject.org/pipermail/tor-relays/2021-May/019649.html [2] https://people.csail.mit.edu/zjn/tor.txt

1 1

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 30 May '21

30 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 28 May '21

28 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 26 May '21

26 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 15 May '21

15 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

Re: [tor-relays] Bridge Transport Issue
by Vlad 12 May '21

12 May '21

>Date: Tue, 11 May 2021 18:49:46 -0500 >From: Kathi <kathihil935(a)gmail.com> >To: tor-relays(a)lists.torproject.org >Subject: [tor-relays] Bridge Transport Issue >Message-ID: <6579c990-2adc-e9e8-d022-d3ad93cdda96(a)gmail.com> >Content-Type: text/plain; charset=utf-8; format=flowed > > ?Pluggable Transport process terminated with status code 256 > > ? ServerTransportPlugin obfs4 exec /user/bin/obfs4proxy > ? ServerTransportListenAddr obfs4 0.0.0.0:XXXX > > ?? Monica Check if you have obfs4proxy package installed. On debian/ubuntu apt install obfs4proxy

1 0

Bridge Transport Issue
by Kathi 12 May '21

12 May '21

Pluggable Transport process terminated with status code 256 ServerTransportPlugin obfs4 exec /user/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:XXXX Monica -- This email has been checked for viruses by AVG. https://www.avg.com

2 1