[tor-relays] Call for setting up new obfs4 bridges

Ben Riley blades1000 at gmail.com
Fri Jul 19 04:36:55 UTC 2019 

Hi,

Thanks for the reply. Yes, I ran that command way back at the start. I'm
assuming I don't have to run it every time the machine reboots or updates?
I ran it again this morning and it made no difference.

Ah logs, you say that like I know where those are :P
When I run sudo tail /var/log/tor/log - I get nothing.
I found the Logs app and run that to get all the system logs - way too much
stuff and I couldn't move it to here, so I found this command (Google) cat
/var/log/syslog | grep tor -i and got the following (I think I've included
2 set of attempts to boot up):

Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Starting with guard context
> "default"
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Signaled readiness to systemd
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bootstrapped 5% (conn):
> Connecting to a relay
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Server managed proxy
> encountered a method error. (obfs4 listen tcp 0.0.0.0:443: bind:
> permission denied)
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Managed proxy at
> '/usr/bin/obfs4proxy' failed the configuration protocol and will be
> destroyed.
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: tor_assertion_failed_(): Bug:
> ../src/feature/client/transports.c:1836: managed_proxy_stdout_callback:
> Assertion mp->conf_state == PT_PROTO_COMPLETED failed; aborting. (on Tor
> 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug: Assertion mp->conf_state
> == PT_PROTO_COMPLETED failed in managed_proxy_stdout_callback at
> ../src/feature/client/transports.c:1836. Stack trace: (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(log_backtrace_impl+0x45) [0x55e1c7174965] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(tor_assertion_failed_+0x94) [0x55e1c716fd24] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(+0xd3f5f) [0x55e1c7045f5f] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(+0x1da363) [0x55e1c714c363] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1e8f8) [0x7f59876138f8] (on
> Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x53f)
> [0x7f598761433f] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(do_main_loop+0xb4) [0x55e1c6fe45e4] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(tor_run_main+0x122d) [0x55e1c6fd18ad] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(tor_main+0x3a) [0x55e1c6fce9ca] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(main+0x19) [0x55e1c6fce559] (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f5985d3cb97]
> (on Tor 0.4.0.5 )
> Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug:
> /usr/bin/tor(_start+0x2a) [0x55e1c6fce5aa] (on Tor 0.4.0.5 )
> Jul 19 14:32:24 ben-OptiPlex-755 systemd[1]: tor at default.service: Main
> process exited, code=dumped, status=6/ABRT
> Jul 19 14:32:24 ben-OptiPlex-755 systemd[1]: tor at default.service: Failed
> with result 'core-dump'.
> Jul 19 14:32:24 ben-OptiPlex-755 systemd[1]: tor at default.service: Service
> hold-off time over, scheduling restart.
> Jul 19 14:32:24 ben-OptiPlex-755 systemd[1]: tor at default.service:
> Scheduled restart job, restart counter is at 74.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Jul 19 14:32:24.374 [notice]
> Tor 0.4.0.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1,
> Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Jul 19 14:32:24.374 [notice]
> Tor can't help you if you use it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Jul 19 14:32:24.374 [notice]
> Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Jul 19 14:32:24.374 [notice]
> Read configuration file "/etc/tor/torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Jul 19 14:32:24.379 [notice]
> Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can
> override this by setting MaxMemInQueues by hand.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28062]: Configuration was valid
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.582 [notice]
> Tor 0.4.0.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1,
> Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.582 [notice]
> Tor can't help you if you use it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.582 [notice]
> Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.582 [notice]
> Read configuration file "/etc/tor/torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.587 [notice]
> Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can
> override this by setting MaxMemInQueues by hand.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.587 [notice]
> Opening Socks listener on 127.0.0.1:9050
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.587 [notice]
> Opened Socks listener on 127.0.0.1:9050
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.587 [notice]
> Opening OR listener on 0.0.0.0:9051
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.588 [notice]
> Opened OR listener on 0.0.0.0:9051
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.588 [notice]
> Opening Extended OR listener on 127.0.0.1:0
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.588 [notice]
> Extended OR listener listening on port 33679.
> Jul 19 14:32:24 ben-OptiPlex-755 tor[28063]: Jul 19 14:32:24.588 [notice]
> Opened Extended OR listener on 127.0.0.1:33679
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Tor 0.4.0.5 running on Linux
> with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.2, and
> Libzstd 1.3.3.
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Tor can't help you if you use
> it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Read configuration file
> "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Read configuration file
> "/etc/tor/torrc".
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Based on detected system
> memory, MaxMemInQueues is set to 2862 MB. You can override this by setting
> MaxMemInQueues by hand.
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opening Socks listener on
> 127.0.0.1:9050
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opened Socks listener on
> 127.0.0.1:9050
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opening OR listener on
> 0.0.0.0:9051
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opened OR listener on
> 0.0.0.0:9051
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opening Extended OR listener
> on 127.0.0.1:0
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Extended OR listener
> listening on port 33679.
> Jul 19 14:32:24 ben-OptiPlex-755 Tor[28063]: Opened Extended OR listener
> on 127.0.0.1:33679
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Parsing GEOIP IPv4 file
> /usr/share/tor/geoip.
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Parsing GEOIP IPv6 file
> /usr/share/tor/geoip6.
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Configured to measure
> statistics. Look for the *-stats files that will first be written to the
> data directory in 24 hours from now.
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Your Tor server's identity
> key fingerprint is 'MelbTORbridge 9F19251CEE17B1E05084898D164F0544CCB095DD'
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Your Tor bridge's hashed
> identity key fingerprint is 'MelbTORbridge
> E4AF099DA5946A6D6EA65DC55B517D3F9B12D0ED'
> Jul 19 14:32:25 ben-OptiPlex-755 Tor[28063]: Bootstrapped 0% (starting):
> Starting
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Starting with guard context
> "default"
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Signaled readiness to systemd
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bootstrapped 5% (conn):
> Connecting to a relay
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Server managed proxy
> encountered a method error. (obfs4 listen tcp 0.0.0.0:443: bind:
> permission denied)
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Managed proxy at
> '/usr/bin/obfs4proxy' failed the configuration protocol and will be
> destroyed.
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: tor_assertion_failed_(): Bug:
> ../src/feature/client/transports.c:1836: managed_proxy_stdout_callback:
> Assertion mp->conf_state == PT_PROTO_COMPLETED failed; aborting. (on Tor
> 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug: Assertion mp->conf_state
> == PT_PROTO_COMPLETED failed in managed_proxy_stdout_callback at
> ../src/feature/client/transports.c:1836. Stack trace: (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(log_backtrace_impl+0x45) [0x55812aa84965] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(tor_assertion_failed_+0x94) [0x55812aa7fd24] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(+0xd3f5f) [0x55812a955f5f] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(+0x1da363) [0x55812aa5c363] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1e8f8) [0x7fefe7a128f8] (on
> Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x53f)
> [0x7fefe7a1333f] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(do_main_loop+0xb4) [0x55812a8f45e4] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(tor_run_main+0x122d) [0x55812a8e18ad] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(tor_main+0x3a) [0x55812a8de9ca] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(main+0x19) [0x55812a8de559] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fefe613bb97]
> (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 Tor[28063]: Bug:
> /usr/bin/tor(_start+0x2a) [0x55812a8de5aa] (on Tor 0.4.0.5 )
> Jul 19 14:32:36 ben-OptiPlex-755 systemd[1]: tor at default.service: Main
> process exited, code=dumped, status=6/ABRT
> Jul 19 14:32:36 ben-OptiPlex-755 systemd[1]: tor at default.service: Failed
> with result 'core-dump'.
> Jul 19 14:32:37 ben-OptiPlex-755 systemd[1]: tor at default.service: Service
> hold-off time over, scheduling restart.
> Jul 19 14:32:37 ben-OptiPlex-755 systemd[1]: tor at default.service:
> Scheduled restart job, restart counter is at 75.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Jul 19 14:32:37.395 [notice]
> Tor 0.4.0.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1,
> Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Jul 19 14:32:37.395 [notice]
> Tor can't help you if you use it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Jul 19 14:32:37.395 [notice]
> Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Jul 19 14:32:37.395 [notice]
> Read configuration file "/etc/tor/torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Jul 19 14:32:37.399 [notice]
> Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can
> override this by setting MaxMemInQueues by hand.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28091]: Configuration was valid
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.590 [notice]
> Tor 0.4.0.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1,
> Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.590 [notice]
> Tor can't help you if you use it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.590 [notice]
> Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.590 [notice]
> Read configuration file "/etc/tor/torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can
> override this by setting MaxMemInQueues by hand.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opening Socks listener on 127.0.0.1:9050
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opened Socks listener on 127.0.0.1:9050
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opening OR listener on 0.0.0.0:9051
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opened OR listener on 0.0.0.0:9051
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opening Extended OR listener on 127.0.0.1:0
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Extended OR listener listening on port 38435.
> Jul 19 14:32:37 ben-OptiPlex-755 tor[28092]: Jul 19 14:32:37.595 [notice]
> Opened Extended OR listener on 127.0.0.1:38435
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Tor 0.4.0.5 running on Linux
> with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.2, and
> Libzstd 1.3.3.
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Tor can't help you if you use
> it wrong! Learn how to be safe at
> https://www.torproject.org/download/download#warning
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Read configuration file
> "/usr/share/tor/tor-service-defaults-torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Read configuration file
> "/etc/tor/torrc".
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Based on detected system
> memory, MaxMemInQueues is set to 2862 MB. You can override this by setting
> MaxMemInQueues by hand.
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opening Socks listener on
> 127.0.0.1:9050
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opened Socks listener on
> 127.0.0.1:9050
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opening OR listener on
> 0.0.0.0:9051
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opened OR listener on
> 0.0.0.0:9051
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opening Extended OR listener
> on 127.0.0.1:0
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Extended OR listener
> listening on port 38435.
> Jul 19 14:32:37 ben-OptiPlex-755 Tor[28092]: Opened Extended OR listener
> on 127.0.0.1:38435
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Parsing GEOIP IPv4 file
> /usr/share/tor/geoip.
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Parsing GEOIP IPv6 file
> /usr/share/tor/geoip6.
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Configured to measure
> statistics. Look for the *-stats files that will first be written to the
> data directory in 24 hours from now.
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Your Tor server's identity
> key fingerprint is 'MelbTORbridge 9F19251CEE17B1E05084898D164F0544CCB095DD'
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Your Tor bridge's hashed
> identity key fingerprint is 'MelbTORbridge
> E4AF099DA5946A6D6EA65DC55B517D3F9B12D0ED'
> Jul 19 14:32:38 ben-OptiPlex-755 Tor[28092]: Bootstrapped 0% (starting):
> Starting
>



On Fri, Jul 19, 2019 at 1:12 AM Philipp Winter <phw at torproject.org> wrote:

> On Thu, Jul 18, 2019 at 12:50:34PM +1000, Ben Riley wrote:
> > Then I saw the above email about being a bridge and thought, fine, I'll
> > configure it to be a bridge and help out someone.
> > Tried to do it via the docker/script method, but soon realised that was
> > outside my skill level (hey stop laughing! :P)
>
> Did you run into any specific issues?  If you had troubles following the
> guide, I'm gonna blame the guide.
>
> > Setting ORPort to 443 as suggested.  I forwarded that port on the
> > router and then tested it, but it said it was closed. So I thought my
> > router was playing up.  I checked a few other ports using online tools
> > and a few of them were closed.  I forwarded a new another port to some
> > other software on another machine and that worked?!  So I realised the
> > ports are open on the router but closed on the ubuntu machine.  I've
> > played around with all the settings, changed by torrc file to a really
> > basic one of:
>
> To run obfs4 on port 443, you will have to run the following command, to
> allow obfs4proxy to bind to port 443:
>
>   sudo setcap cap_net_bind_service=+ep /usr/bin/obfs4proxy
>
> If you did that already, it would be helpful to see your logs.
>
> Cheers,
> Philipp
> _______________________________________________
> 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/20190719/605da209/attachment-0001.html>

More information about the tor-relays mailing list