[tor-relays] Moving my obfs4 bridge from tor expert bundle to Debian, and have some questions. Thanks.
Keifer Bly
keifer.bly at gmail.com
Mon Mar 30 05:48:47 UTC 2020
Forgot to paste the unattended upgrades file sorry:
Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
"origin=TorProject";
};
Unattended-Upgrade::Package-Blacklist {
};
Unattended-Upgrade::Automatic-Reboot "true";
--Keifer
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sun, Mar 29, 2020 at 10:45 PM Keifer Bly <keifer.bly at gmail.com> wrote:
> Here is tors log:
>
> Mar 29 17:00:46.000 [notice] Tor 0.4.2.7 opening new log file.
> Mar 29 17:00:46.899 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 17:00:46.900 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 17:00:46.901 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 17:00:46.902 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
> Mar 29 17:00:46.902 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 17:00:46.905 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 17:00:46.905 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 17:00:46.906 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 17:00:46.907 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 17:00:46.908 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 17:00:46.916 [notice] Extended OR listener listening on port 50727.
> Mar 29 17:00:46.917 [notice] Opened Extended OR listener on 127.0.0.1:50727
> Mar 29 17:00:46.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 17:00:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
> Mar 29 17:00:47.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
> Mar 29 17:00:47.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.
> Mar 29 17:00:47.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
> Mar 29 17:00:47.000 [notice] You are running a new relay. Thanks for helping the Tor network! If you wish to know what will happen in the upcoming weeks regarding its usage, have a look at https://blog.torproject.org/blog/lifecycle-of-a$Mar 29 17:00:47.000 [notice] It looks like I need to generate and sign a new medium-term signing key, because I don't have one. To do that, I need to load (or create) the permanent master identity key. If the master identity key was not$Mar 29 17:00:47.000 [notice] Your Tor server's identity key fingerprint is 'torland 7DBC1875771B54F4FE40EB376460EF557EE9E884'
> Mar 29 17:00:47.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 780F4E3ADBC574A63CE8155C0911E0A06BA3331D'
> Mar 29 17:00:47.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 29 17:00:48.000 [notice] Starting with guard context "default"
> Mar 29 17:00:48.000 [notice] Registered server transport 'obfs4' at '[::]:443'
> Mar 29 17:00:50.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
> Mar 29 17:00:51.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 29 17:00:51.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 29 17:00:51.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
> Mar 29 17:00:51.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
> Mar 29 17:00:51.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
> Mar 29 17:00:51.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
> Mar 29 17:00:52.000 [notice] Guessed our IP address as 24.176.251.66 (source: 107.189.10.156).
> Mar 29 17:00:53.000 [notice] Bootstrapped 100% (done): Done
> Mar 29 17:00:53.000 [notice] Now checking whether ORPort 24.176.251.66:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
> Mar 29 17:00:54.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Mar 29 17:01:00.000 [notice] Performing bandwidth self-test...done.
> Mar 29 17:01:42.000 [notice] Catching signal TERM, exiting cleanly.
> Mar 29 17:05:13.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 17:05:13.906 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 17:05:13.907 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 17:05:13.909 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 17:05:13.910 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 17:05:13.912 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 17:05:13.912 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 17:05:13.913 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 17:05:13.913 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 17:05:13.914 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 17:05:13.917 [notice] Extended OR listener listening on port 50756.
> Mar 29 17:05:13.917 [notice] Opened Extended OR listener on 127.0.0.1:50756
> Mar 29 17:05:13.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 17:05:13.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
> Mar 29 17:05:14.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
>
> Mar 29 17:05:15.000 [notice] Starting with guard context "default"
> Mar 29 17:05:15.000 [notice] Registered server transport 'obfs4' at '[::]:443'
> Mar 29 17:05:16.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
> Mar 29 17:05:16.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
> Mar 29 17:05:16.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
> Mar 29 17:05:16.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
> Mar 29 17:05:16.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
> Mar 29 17:05:17.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
> Mar 29 17:05:17.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
> Mar 29 17:05:18.000 [notice] Bootstrapped 100% (done): Done
> Mar 29 17:05:19.000 [notice] Guessed our IP address as 24.176.251.66 (source: 188.165.220.34).
> Mar 29 17:05:21.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Mar 29 17:05:26.000 [notice] Performing bandwidth self-test...done.
> Mar 29 17:22:25.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
> Mar 29 17:22:25.000 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 17:22:25.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 17:22:25.000 [warn] Pluggable Transport process terminated with status code 1
> Mar 29 17:45:08.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 17:45:08.947 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 17:45:08.948 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Mar 29 17:45:08.949 [notice] Read configuration file "/etc/tor/torrc". Mar 29 17:45:08.951 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 17:45:08.952 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 17:45:08.952 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 17:45:08.953 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 17:45:08.954 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 17:45:08.954 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 17:45:08.955 [notice] Extended OR listener listening on port 50889. Mar 29 17:45:08.956 [notice] Opened Extended OR listener on 127.0.0.1:50889 Mar 29 17:45:08.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 17:45:08.000 [warn] It looks like another Tor process is running with the same data directory. Waiting 5 seconds to see if it goes away.
> Mar 29 17:45:13.000 [err] No, it's still there. Exiting.
> Mar 29 17:45:13.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.2.7 )
> Mar 29 17:45:13.000 [err] Reading config failed--see warnings above.
> Mar 29 19:55:41.000 [notice] Catching signal TERM, exiting cleanly.
> Mar 29 20:05:32.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 20:05:32.499 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 20:05:32.500 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 20:05:32.501 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 20:05:32.502 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 20:05:32.503 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 20:05:32.503 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 20:05:32.504 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 20:05:32.504 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 20:05:32.504 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 20:05:32.505 [notice] Extended OR listener listening on port 51493.
> Mar 29 20:05:32.507 [notice] Opened Extended OR listener on 127.0.0.1:51493
> Mar 29 20:05:32.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 20:05:32.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
> Mar 29 20:05:32.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
> Mar 29 20:05:33.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.
> Mar 29 20:05:33.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
> Mar 29 20:05:33.000 [notice] Your Tor server's identity key fingerprint is 'torland 7DBC1875771B54F4FE40EB376460EF557EE9E884'
> Mar 29 20:05:33.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 780F4E3ADBC574A63CE8155C0911E0A06BA3331D'
> Mar 29 20:05:33.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 29 20:05:37.000 [notice] Starting with guard context "default"
> Mar 29 20:05:37.000 [notice] Registered server transport 'obfs4' at '[::]:443'
> Mar 29 20:05:38.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
>
>
> Mar 29 20:16:42.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't. Mar 29 20:16:42.000 [notice] Your Tor server's identity key fingerprint is 'torland 7DBC1875771B54F4FE40EB376460EF557EE9E884' Mar 29 20:16:42.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 780F4E3ADBC574A63CE8155C0911E0A06BA3331D'
> Mar 29 20:16:42.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 29 20:16:46.000 [notice] Starting with guard context "default"
> Mar 29 20:16:46.000 [notice] Registered server transport 'obfs4' at '[::]:443'
> Mar 29 20:16:47.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
> Mar 29 20:16:47.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
> Mar 29 20:16:47.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
> Mar 29 20:16:48.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
> Mar 29 20:16:48.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
> Mar 29 20:16:48.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
> Mar 29 20:16:48.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
> Mar 29 20:16:48.000 [notice] Guessed our IP address as 24.176.251.66 (source: 188.165.220.34).
> Mar 29 20:16:49.000 [notice] Bootstrapped 100% (done): Done
> Mar 29 20:16:49.000 [notice] Now checking whether ORPort 24.176.251.66:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
> Mar 29 20:16:51.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Mar 29 20:18:06.000 [notice] Performing bandwidth self-test...done.
> Mar 29 20:20:27.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 20:20:27.693 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 20:20:27.694 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 20:20:27.696 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 20:20:27.697 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 20:20:27.698 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 20:20:27.699 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 20:20:27.699 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 20:20:27.700 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 20:20:27.701 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 20:20:27.701 [notice] Extended OR listener listening on port 51834.
> Mar 29 20:20:27.702 [notice] Opened Extended OR listener on 127.0.0.1:51834
> Mar 29 20:20:27.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 20:20:27.000 [warn] It looks like another Tor process is running with the same data directory. Waiting 5 seconds to see if it goes away.
> Mar 29 20:20:32.000 [err] No, it's still there. Exiting.
> Mar 29 20:20:32.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.2.7 )
> Mar 29 20:20:32.000 [err] Reading config failed--see warnings above.
> Mar 29 22:13:39.000 [notice] Catching signal TERM, exiting cleanly.
> Mar 29 22:14:55.000 [notice] Tor 0.4.2.7 opening log file.
> Mar 29 22:14:55.638 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 22:14:55.639 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 22:14:55.639 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 22:14:55.641 [notice] Based on detected system memory, MaxMemInQueues is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 22:14:55.641 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 22:14:55.642 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 22:14:55.642 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 22:14:55.642 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 22:14:55.643 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 22:14:55.644 [notice] Extended OR listener listening on port 55133.
> Mar 29 22:14:55.645 [notice] Opened Extended OR listener on 127.0.0.1:55133
> Mar 29 22:14:55.000 [notice] Not disabling debugger attaching for unprivileged users.
> Mar 29 22:14:55.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
> Mar 29 22:14:55.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
> Mar 29 22:14:56.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. Mar 29 22:14:56.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't. Mar 29 22:14:56.000 [notice] Your Tor server's identity key fingerprint is 'torland 7DBC1875771B54F4FE40EB376460EF557EE9E884'
> Mar 29 22:14:56.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 780F4E3ADBC574A63CE8155C0911E0A06BA3331D'
> Mar 29 22:14:56.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 29 22:15:00.000 [notice] Starting with guard context "default"
> Mar 29 22:15:00.000 [notice] Registered server transport 'obfs4' at '[::]:443'
>
> ^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos M-U Undo M-A Mark Text M-] To Bracket M-Q Previous ^B Back ^Left Prev Word ^A Home
> ^X Exit ^R Read File ^\ Replace ^U Uncut Text
>
> Mar 29 22:15:01.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
> Mar 29 22:15:01.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 29 22:15:01.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 29 22:15:01.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
> Mar 29 22:15:01.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
> Mar 29 22:15:01.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
> Mar 29 22:15:01.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
> Mar 29 22:15:02.000 [notice] Guessed our IP address as 24.176.251.66 (source: 188.165.220.34).
> Mar 29 22:15:03.000 [notice] Bootstrapped 100% (done): Done
> Mar 29 22:15:03.000 [notice] Now checking whether ORPort 24.176.251.66:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
> Mar 29 22:15:05.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Mar 29 22:16:13.000 [notice] Performing bandwidth self-test...done.
>
> I might have copied some of the log twice. Sorry about that.
>
> After installing unattended upgrades, here is what is in my 50unatennded-upgrades file, as torproject.org steps for configuring updates for tor recommended. Thank you, I wonder why the upgrades are not working.
>
> --Keifer
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> <#m_-8360668559380116446_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Sun, Mar 29, 2020 at 9:00 PM teor <teor at riseup.net> wrote:
>
>> Hi,
>>
>> On 30 Mar 2020, at 13:45, Keifer Bly <keifer.bly at gmail.com> wrote:
>>
>> So I am switching the OBFS4 bridge I was running via Tor Expert Bundle on
>> Windows 10 over to running it via Debian app for Windows 10.
>>
>> This app is on the Windows store at
>> https://www.microsoft.com/en-us/p/debian/9msvkqc78pk6?activetab=pivot:overviewtab
>>
>> Essentially, it is an app that lets you run Linux packages on Windows. I
>> made the switch so that I could keep tor and obfs4 up to date using
>> unattended upgrades.
>>
>> However, for some odd reason, despite the fact I backed up the tor
>> identity keys and pasted them into the keys directory when I moved over,
>> the bridge is still generating new keys on startup. I copied the key files
>> from my expert bundle bridge to
>>
>> /var/lib/tor/keys directory in the Linu terminal, I copied all of the
>> files. It’s a bridge so no big deal I guess, but wonder why that is
>> happening.
>>
>> Please show us the tor logs.
>>
>>
>> https://metrics.torproject.org/rs.html#details/780F4E3ADBC574A63CE8155C0911E0A06BA3331D
>>
>> And, I tested to see of unattended upgrades was working correctly after
>> configuring it with these instructions:
>>
>>
>> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates
>>
>>
>>
>> And got this the attached photo as a result, does this mean it is keeping
>> tor and obfs4 up to date?
>> tor update test.PNG
>> <https://drive.google.com/file/d/1c5TinBlApx5YuObiwt8pkl9w_F74O0JL/view?usp=drive_web>
>>
>>
>> Please use a pastebin for logs, or paste the text in your email.
>> https://paste.debian.net is good.
>>
>> Looks like updates aren't working, do you see the line that says:
>> Sanity check failed
>>
>> T
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20200329/91c9ea7f/attachment-0001.html>
More information about the tor-relays
mailing list