- tor-relays - lists.torproject.org

Migrating to CentOS8
by Totor be 09 Nov '19

09 Nov '19

Hi folks I'm considering migrating my relays from CentOS 7 to CentOS 8 and upgrading tor from 0.3.5.8 to 0.4.1.6 One small VM relay at home is running the C8/0.4 setup and seems to be ok According to bodhi, this is supposed to be stable https://bodhi.fedoraproject.org/updates/?packages=tor Before migrating the others, I prefer to cross-check: is there anyone aware of issues with C8 and tor 0.4.x?? Thanks! <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

3 2

"large number of connections to other relays" - What should I do?
by Akarin 09 Nov '19

09 Nov '19

Hi I'm running a new non-exit relay on my server which has a shared address, and I often see the following message in my log file: Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Do I have to worry about that? If the answer is yes, what should I do?

2 1

The Onion Box v19.2: Dashboard to monitor Tor node operations
by theonionbox＠gmx.com 09 Nov '19

09 Nov '19

2 3

Tor stop / reboot by itself + weird logs (hacking?)
by David Strappazon 08 Nov '19

08 Nov '19

Hello everyone, i'm running a bridge on a raspberry Pi 3B+ on Kali Linux. Everything looks fine but after checking the logs i noticed that the service rebooted by itself in the middle on the night: Nov 06 03:51:09.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Nov 06 03:51:10.000 [notice] Delaying directory fetches: We are hibernating or shutting down. Nov 06 03:51:39.000 [notice] Clean shutdown finished. Exiting. etc... Then after that, it works again (will check tonight /tomorrow if it reboots again). I'm trying to find why it is rebooting but without success. I checked all logs possible and also notice this in journalctl -xe: nov. 06 19:37:58 kali-pi sshd[15920]: Failed password for root from XXXXX port 37494 ssh2 nov. 06 19:38:03 kali-pi sshd[15920]: Failed password for root from XXXX port 37494 ssh2 nov. 06 19:38:08 kali-pi sshd[15920]: Failed password for root from XXXXX port 37494 ssh2 nov. 06 19:38:13 kali-pi sshd[15920]: Failed password for root from XXXXX port 37494 ssh2 nov. 06 19:38:18 kali-pi sshd[15920]: Failed password for root from XXXXX port 37494 ssh2 nov. 06 19:38:18 kali-pi sshd[15920]: error: maximum authentication attempts exceeded for root from 21> nov. 06 19:38:18 kali-pi sshd[15920]: Disconnecting authenticating user root 2XXXX port 37494: > nov. 06 19:38:18 kali-pi sshd[15920]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ss> nov. 06 19:38:18 kali-pi sshd[15920]: PAM service(sshd) ignoring max retries; 6 > 3 nov. 06 19:38:21 kali-pi sshd[15950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid> nov. 06 19:38:22 kali-pi sshd[15953]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid> nov. 06 19:38:23 kali-pi sshd[15950]: Failed password for root from XXXX port 64786 ssh2 nov. 06 19:38:23 kali-pi sshd[15953]: Failed password for root from XXXXX port 6739 ssh2 There's two different IP that i don't know. A whois says it's a Chinese provider... Should i consider that someone is trying to break into my home network? Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 2

Tor stopped suddenly - clock/time issue
by David Strappazon 07 Nov '19

07 Nov '19

Hi, while checking my (new)or not this is what i saw in notices.log Nov 05 05:18:57.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Nov 05 10:44:17.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Nov 05 10:44:18.000 [notice] Delaying directory fetches: We are hibernating or shutting down. Nov 05 10:44:47.000 [notice] Clean shutdown finished. Exiting. Apr 11 18:28:44.000 [notice] Tor 0.4.1.6 opening log file. Apr 11 18:28:44.103 [notice] Tor 0.4.1.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.3. Apr 11 18:28:44.103 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Apr 11 18:28:44.103 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Apr 11 18:28:44.103 [notice] Read configuration file "/etc/tor/torrc". Apr 11 18:28:44.125 [notice] Based on detected system memory, MaxMemInQueues is set to 694 MB. You can override this by setting MaxMemInQueues by hand. Apr 11 18:28:44.128 [notice] Opening Socks listener on 127.0.0.1:9050 Apr 11 18:28:44.128 [notice] Opened Socks listener on 127.0.0.1:9050 Apr 11 18:28:44.128 [notice] Opening OR listener on 0.0.0.0:4433 Apr 11 18:28:44.128 [notice] Opened OR listener on 0.0.0.0:4433 Apr 11 18:28:44.128 [notice] Opening Extended OR listener on 127.0.0.1:0 Apr 11 18:28:44.128 [notice] Extended OR listener listening on port 40247. Apr 11 18:28:44.128 [notice] Opened Extended OR listener on 127.0.0.1:40247 Apr 11 18:28:44.000 [notice] Bootstrapped 0% (starting): Starting Apr 11 18:28:44.000 [warn] Received local state file with skewed time (/var/lib/tor/state): It seems that our clock is behind by 207 days, 17 hours, 16 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Apr 11 18:28:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17946963 in local state file from /var/lib/tor/state; CLOCK_SKEW; count 1; recommendation warn; host ? at ?) Nov 05 10:45:34.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Nov 05 10:45:35.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Nov 05 10:45:35.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Nov 05 10:45:43.000 [notice] Your Tor server's identity key fingerprint is 'citizenfour B839503CA8F877D0263A38103DAF47EF302FBCF7' Nov 05 10:45:43.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'citizenfour 9D1CCBE7EEF99FCCA6F767838FA08B23DDFABB3A' Nov 05 10:45:44.000 [warn] Our clock is 207 days, 16 hours, 31 minutes behind the time published in the consensus network status document (2019-11-05 09:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings! Nov 05 10:45:44.000 [warn] Received ns flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 207 days, 16 hours, 31 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 05 10:45:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17944276 in ns flavor consensus from CONSENSUS; CLOCK_SKEW; count 2; recommendation warn; host ? at ?) Nov 05 10:45:45.000 [warn] Our clock is 207 days, 15 hours, 31 minutes behind the time published in the consensus network status document (2019-11-05 08:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings! Nov 05 10:45:45.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 207 days, 15 hours, 31 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 05 10:45:45.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17940676 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 3; recommendation warn; host ? at ?) Nov 05 10:47:44.000 [notice] Starting with guard context "default" Nov 05 10:47:44.000 [notice] Signaled readiness to systemd Nov 05 10:47:44.000 [notice] Registered server transport 'obfs4' at '[::]:1234' Nov 05 10:47:45.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Nov 05 10:47:45.000 [notice] Opening Socks listener on /run/tor/socks Nov 05 10:47:45.000 [notice] Opened Socks listener on /run/tor/socks Nov 05 10:47:45.000 [notice] Opening Control listener on /run/tor/control Nov 05 10:47:45.000 [notice] Opened Control listener on /run/tor/control Nov 05 10:47:45.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Nov 05 10:47:47.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Nov 05 10:47:48.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Nov 05 10:47:48.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Nov 05 10:47:48.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits Nov 05 10:47:48.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Nov 05 10:47:48.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Nov 05 10:47:48.000 [notice] Guessed our IP address as 78.224.250.217 (source: 213.220.220.60). Nov 05 10:47:51.000 [notice] Bootstrapped 100% (done): Done Nov 05 10:47:51.000 [notice] Now checking whether ORPort 78.224.250.217:4433 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Nov 05 10:47:51.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Nov 05 10:47:53.000 [notice] Performing bandwidth self-test...done. Nov 05 13:12:01.000 [notice] New control connection opened. root@kali-pi:/var/log/tor# When i type date, everything look fine but when i first set up my raspberry Pi3b+ (os: Kali linux) i had a hard time getting the right time /timezone. It looks like at boot it takes like 30s to get the right time. Any idea how to fix this and avoid futur issue? Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 3

Minimum traffic for a relay to be helpful to the network
by Keifer Bly 06 Nov '19

06 Nov '19

Hello list, So a while back, I was attempting to run a relay via Google Cloud, but had trouble finding an appropriate speed without having to spend a huge amount of money on outbound traffic. I am wondering what would be a good amount to dedicate to the relay while keeping it inexpensive to run: Here is Google Clouds pricing plans https://cloud.google.com/network-tiers/pricing It appears they charge a few cents a gigabyte, thx. --Keifer

3 2

Backup the Fingerprint
by Kolja Sagorski 04 Nov '19

04 Nov '19

Hello, can anyone help me to backup the fingerprint on debian10?

2 1

First time configuring a bridge - no log - doesnt work
by David Strappazon 04 Nov '19

04 Nov '19

Hi, I want to configure a tor obfs4 bridge on a raspberry pi 3B+. My system is Kali Linux. I followed this documentation: https://community.torproject.org/relay/setup/bridge/debian-ubuntu/ Actually, when i want to check the log in /var/log/tor, the folder is empty. TOr is running but nothing happens. here's my torrc file : RunAsDaemon 1 BridgeRelay 1 Log notice file /var/log/tor/notices.log Log debug file /var/log/tor/debug.log Log notice syslog Log debug stderr # Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. ORPort 4433 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy # Replace "TODO2" with an obfs4 port of your choice. This port must be # externally reachable and must be different from the one specified for ORPort. # Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. ServerTransportListenAddr obfs4 0.0.0.0:1234 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port number, nor listen on 0.0.0.0. ExtORPort auto # Replace "<address(a)email.com>" with your email address so we can contact you if there are problems with your bridge. # This is optional but encouraged. ContactInfo ################# # Pick a nickname that you like for your bridge. This is optional. Nickname RageAgainstTheMachine ExitPolicy reject *:* I've tried to check everything but i can't find why it doesn't work. Any help / advice would be appreciated. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

jumps of the amount of network connections
by Toralf Förster 04 Nov '19

04 Nov '19

I'm curious how to interpret the curves as seen in the attachment. The measurment were made at a stable fast relay in the past. -- Toralf

1 0

Multiple Tor instances
by nottryingtobelame＠protonmail.com 02 Nov '19

02 Nov '19

I have read that it is possible to run multiple bridges on the same IP using different ports and multiple instances of Tor. If this is the case, is there a guide, or can anyone provide instructions, for how to setup multiple instances of Tor on the same machine? Thanks in advance.

1 0

Issues reaching gigabit relay speeds
by Mitar 01 Nov '19

01 Nov '19

Hi! I have a gigabit connection and I am trying to utilize it as much as possible as a Tor relay. When I try various speed tests I get on the machine speeds close to gigabit, but when running Tor, I do not achieve anything close to it. I even started two Tor nodes on the same machine/connection, see here: https://metrics.torproject.org/rs.html#details/567E9785458C605E59202755C748… https://metrics.torproject.org/rs.html#details/4CF9BAEB0DE6D7230D6B7DA0FF42… The utilization of the machine is pretty low, top returns: top - 20:27:33 up 4 days, 23:01, 1 user, load average: 0.32, 0.28, 0.23 Tasks: 167 total, 1 running, 97 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.6 us, 0.6 sy, 0.0 ni, 97.3 id, 0.0 wa, 0.0 hi, 0.5 si, 0.0 st KiB Mem : 3772912 total, 931336 free, 1574676 used, 1266900 buff/cache KiB Swap: 3900412 total, 3900412 free, 0 used. 1915568 avail Mem In configuration I have: RelayBandwidthRate 125 MB RelayBandwidthBurst 125 MB Interesting is that it seems each Tor daemon on same machine runs always around 5 MiB/s, when I started the second one, it just added to it with another 5 MiB/s. So it is somewhere else where is the bottleneck? What could I do to improve things here? To me it looks like more throughput should be possible? Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m

4 4

DDoS’d offline
by Christopher Sheats 31 Oct '19

31 Oct '19

fyi https://twitter.com/EmeraldOnion/status/1189668679752900608 Calyx appears to have been hit also, but not offline https://twitter.com/calyxinstitute/status/1189693027192840192 -- Christopher Sheats Executive Director for Emerald Onion Email: yawnbox(a)emeraldonion.org Office (& Signal): +1-206-739-3390 Website: https://emeraldonion.org/

2 2

New relay in USA: bridge or middle relay?
by Isaac Grover, Aileron I.T. 31 Oct '19

31 Oct '19

Good morning from Wisconsin, After reading about how middle relays in the USA go largely underutilized, and having quietly run my own middle relay for several years, would it be more beneficial to the network to launch several new bridges instead of more middle relays? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - " Because #ProactiveIsBetter " O: 715-377-0440, F:715-690-1029, W: www.aileronit.com

3 3

Re: [tor-relays] Windows Relay Setup
by William Pate 31 Oct '19

31 Oct '19

I finally got around to playing with this some more. Thank you for your message, Bruce. I searched for Vidalia and found an old bundle that appears to work perfectly on my Windows 10 machine. Steps I took: 1. Download Vidalia Bundle 0.2.4.23 from http://vidalia-bundle.en.lo4d.com/ 2. Extract 3. Install 4. Start 5. The Vidalia Control Panel will pop-up 6. In settings, I changed the Tor executable from the one included with the Vidalia Bundle to the current version of Tor elsewhere on my system. Like I said, it *appears* to be working. Can't find it in relay search yet, but I only set it up moments ago. Nickname is inadequate Contact is willpate(a)disroot.org William Pate willpate(a)pm.me 512-947-3311 inadequate.net ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, July 14, 2019 1:44 AM, Barton Bruce <barton.bruce(a)gmail.com> wrote: > > > William, > > On 7/11/2019 6:58 PM, William Pate wrote: > > > I'm interested in hosting a Windows-based relay, if anyone can point me to a good tutorial. I've tried the most common ones. > > > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > There used to be a VIDALIA (sp?) kit that could simply be downloaded and > run on a windows machine. I then worked for an ISP/CLEC and had lots of > bandwidth so ran Vidaalia on a 64 bit Windows 7 Ultimate machine on my > desk at work. > > I never did hear why something had changed at the tor project so that > stopped working, but do remember a rude snippy condescending reply from > someone on the mailing list so I lost interest. > > I did get the head Tor guy from the Central Square Cambridge office of > TOR to come speak at a local networking group's monthly meeting we held > at a MicroSlush faclity in Burlington, MA and it was well received by a > packed audience. I think he now has left TOR and works for some ISP. > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus

4 4

Setting up tor/relay
by hawkeye6666 31 Oct '19

31 Oct '19

Hello everybody! I am using a windows ten computer on my home network. I would like to donate some of my bandwith but dont know how to do it. As i read in the tor wiki, as I have a static IPadress I should use a bridge. But I have no idea how so if anyone got a good tutorial please let me know.

2 1

Source code signature verification
by tor_manager＠autistici.org 30 Oct '19

30 Oct '19

Hello everyone, I am looking for the procedure and the tor developer key to verify tor source code package. I found the one about tor-browser but not this. Thanks a lot, Andrea

2 2

Question
by Rubles 30 Oct '19

30 Oct '19

I tried running a bridge but my systemLog said: Please upgrade! This version of Tor (0.3.2.10) is not recommended, according to the directory authorities. Recommended versions are: 0.2.9.15,0.2.9.16,0.2.9.17,0.3.5.8,0.4.0.5,0.4.0.6,0.4.1.2-alpha,0.4.1.3-alpha,0.4.1.4-rc,0.4.1.5,0.4.1.6,0.4.1.7,0.4.2.1-alpha,0.4.2.2-alpha,0.4.2.3-alpha (I used sudo apt-get install tor - on Mint) so I checked out https://support.torproject.org/apt/tor-deb-repo/ and when I tried gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - it didn't work as it said gpg: WARNING: unsafe ownership on homedir gpg: [stdout]: write error: Broken pipe gpg: build_packet(2) failed: Broken pipe gpg: key export failed: Broken pipe Here are some other things it said: Looks like client functionality is working. Bootstrapped 100%: Done Your server has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. What do I do?

2 1

36C3 voucher
by Niels Hesse 28 Oct '19

28 Oct '19

Anybody holding a Voucher for 34C3 in Leipzig at the end of December? https://tickets.events.ccc.de/36c3/docs/ <https://tickets.events.ccc.de/34c3/docs/>? While still running several Exits I would be more than happy to meet others there Thanks

2 1

Tor can exceed your AccountingMax in 0.4.0+
by Roger Dingledine 24 Oct '19

24 Oct '19

Hello wonderful relay operators, I wanted to let you know about a bug that might affect you if you use the AccountingMax option, in Tor 0.4.0 and later. Here's the ChangeLog entry from the upcoming 0.4.2.3-alpha: o Major bugfixes (relay): - Relays now respect their AccountingMax bandwidth again. When relays entered "soft" hibernation (which typically starts when we've hit 90% of our AccountingMax), we had stopped checking whether we should enter hard hibernation. Soft hibernation refuses new connections and new circuits, but the existing circuits can continue, meaning that relays could have exceeded their configured AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha. That is, when your relay enters "soft" hibernation, you stop accepting new connections and new circuits (good), but you stop checking whether you've hit the hard limit and need to close down the remaining circuits (bad). The bug has the additional impact that when your Tor has entered soft hibernation, it stops updating the 'state' file in its DataDirectory, which means it doesn't record new bytes spent in the interval after that point. You can read more details on the trac ticket: https://bugs.torproject.org/32108 We'll have an 0.4.2.3-alpha release out soon with what we hope is a fix. And if it looks good then we'll plan to put out new 0.4.0.6 and 0.4.1.7 stables. In the meantime, if this bug affects you, you might do some combination of the following: * Watch your relay's bandwidth use and logs more carefully than usual * Downgrade to Tor 0.3.5.8 until the newer stables are ready * Set your RelayBandwidthRate to a lower value so you don't hit soft hibernation as quickly during this interval * Apply the two-line patch yourself (and let us know whether anything breaks) Sorry for the troubles, --Roger

1 0

public open socks port
by ylms 24 Oct '19

24 Oct '19

Hello all, I am wondering if there is any reason why one should not open the socks port of Tor to the public internet? I mean I run a Tor exit or relay, so why should I not open the port and give it to people that can't install Tor on some devices? Thanks for your thoughts. yl

4 3

Tor Relay on Pi Up
by William Pate 23 Oct '19

23 Oct '19

Put one up on my Raspberry Pi using the directions at https://community.torproject.org/relay/setup/bridge/debian-ubuntu/: https://metrics.torproject.org/rs.html#details/F38EE238CCB90EE18EC63361CB45… William Pate willpate(a)pm.me 512-947-3311 inadequate.net

1 0

Shit happens
by lists＠for-privacy.net 23 Oct '19

23 Oct '19

Ohh fuck. Too many terminals open and in the wrong: "rm -R / var / lib / tor-instances" I idiot of course have _no_ backup of the keys. :-( -- ╰_╯ Ciao Marco! My family:6D6EC2A2E2ED8BFF2D4834F8D669D82FC2A9FA8D

1 0

Operator straw poll: Reasons why you use Tor LTS versions?
by Mike Perry 22 Oct '19

22 Oct '19

Hello relay operators, Thanks for running relays, and thanks to those of you who are moving off of our old EOL Tor versions. Thanks especially to those of you who moved directly to Tor 0.4.1! We would like to transition the LTS Tor to be for use in edge/client/non-relay infrastructure only. We would like to minimize even that use. We need to update our network protocols to improve performance, security, and to add defenses against DoS attacks. Doing this while supporting LTS for relays is expensive, especially when large backports must be done to keep the network safe. It also slows down the uniform deployment of performance improvements, which contributes to the frustrating user experience of abysmal-but-rare performance edge cases. Unfortunately, we still have something like 2500 relays on either Tor 0.2.9-LTS or Tor 0.3.5-LTS. What are the reasons for this? My guess is the top 5 most common responses are: 1. "I didn't know that Debian's backports repo has latest-stable Tor!" 2. "I didn't see the Tor Project repos mentioned in Tor's Relay docs!" 3. "I'm running a distribution that Tor Project doesn't have repos for." 4. "I rolled my own custom Tor from git and forgot about it." 5. "My relay machine was not getting any updates at all. Oops." Does anyone have a reason that they think many other relay operators also share? How can we fix that for you, or at least, how can we make it easier to run the very latest stable series Tor on your relay? -- Mike Perry

10 17

Install on Tor on fresh Debian 10 failed (gpg key invalid)
by Olaf Grimm 21 Oct '19

21 Oct '19

Hello! I updated my VPS with a fresh Debian 10 install. According procedure in the documentation 'curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E8… | gpg --import' I get the error message '2019-10-17 20:34:32 (1.01 MB/s) - ‘A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc’ saved [19665/19665] gpg: no valid OpenPGP data found. gpg: Total number processed: 0 What is going wrong? Is this an invalid key? After weeks ago my other install on Debian 10 was ok. Best regards! Olaf

4 5

DDNS with Relays and/or Bridges?
by nottryingtobelame＠protonmail.com 20 Oct '19

20 Oct '19

Forgive me if this is a dumb or newbie question, but can DDNS be used with either relays or bridges? I was considering setting up DDNS with FreeDNS mostly for my bridge so that if the IP changes (I have chosen not to subscribe to a static IP with my ISP), my clients can still access the bridge, rather than having to reset and start the bridge from scratch. Obviously I would not make it "torbridge.anonymousnetwork.com" or anything that would suggest its true use. Maybe something like "photoserver.whatever.com" or something like that. If DDNS can be used, my follow-up question is where all would I need to set that information? I'm guessing just in torrc? I do not remember the flag for identifying your IP, as I've always left it blank for Tor to guess, but could the DDNS hostname be entered here in lieu of the IP? Thanks for your time.

3 2