tor-relays

tor-relays@lists.torproject.org

42 participants
4821 discussions

Start a nNew thread

A report on running a bridge on google cloud
by Keifer Bly 03 May '21

03 May '21

4 5

tor bridge on FreeBSD silently stops working
by torbridge＠wp1180731.server-he.de 02 May '21

02 May '21

Hi, I am trying to run a bridge with 0.4.5.7 on FreeBSD since a couple of weeks. Everything seems fine for a few days and then my bridge is reported offline on metrics.torproject.org. There are only notice messages in the logs and after a restart everything seems fine again (for a few days). Attached are the complete logs for a full cycle. Any ideas? Thanks! BR, CoS Apr 23 17:55:02.000 [notice] Tor 0.4.5.7 opening log file. Apr 23 17:55:02.841 [notice] We compiled with OpenSSL 1010108f: OpenSSL 1.1.1h-freebsd 22 Sep 2020 and we are running with OpenSSL 1010108f: 1.1.1h-freebsd. These two versions sh> Apr 23 17:55:02.846 [notice] Tor 0.4.5.7 running on FreeBSD with Libevent 2.1.12-stable, OpenSSL 1.1.1h-freebsd, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Unknown N/A as libc. Apr 23 17:55:02.846 [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 23 17:55:02.846 [notice] Read configuration file "/usr/local/etc/tor/torrc". Apr 23 17:55:02.847 [notice] Based on detected system memory, MaxMemInQueues is set to 8192 MB. You can override this by setting MaxMemInQueues by hand. Apr 23 17:55:02.849 [notice] Opening Socks listener on 127.0.0.1:9050 Apr 23 17:55:02.849 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050 Apr 23 17:55:02.849 [notice] Opening OR listener on 0.0.0.0:59001 Apr 23 17:55:02.849 [notice] Opened OR listener connection (ready) on 0.0.0.0:59001 Apr 23 17:55:02.849 [notice] Opening Extended OR listener on 127.0.0.1:0 Apr 23 17:55:02.849 [notice] Extended OR listener listening on port 12450. Apr 23 17:55:02.849 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:12450 Apr 23 17:55:08.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Apr 23 17:55:08.000 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Apr 23 17:55:08.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. Apr 23 17:55:08.000 [notice] Your Tor server's identity key fingerprint is '...' Apr 23 17:55:08.000 [notice] Your Tor bridge's hashed identity key fingerprint is '...' Apr 23 17:55:08.000 [notice] Your Tor server's identity key ed25519 fingerprint is '...' Apr 23 17:55:08.000 [notice] Bootstrapped 0% (starting): Starting Apr 23 17:55:13.000 [notice] Starting with guard context "default" Apr 23 17:55:14.000 [notice] Registered server transport 'obfs4' at '[::]:59002' Apr 23 17:55:15.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Apr 23 17:55:15.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Apr 23 17:55:15.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Apr 23 17:55:15.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Apr 23 17:55:15.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Apr 23 17:55:15.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Apr 23 17:55:15.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Apr 23 17:55:15.000 [notice] Bootstrapped 100% (done): Done Apr 23 17:55:15.000 [notice] Now checking whether IPv4 ORPort <IP>:59001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Apr 23 17:55:15.000 [notice] Self-testing indicates your ORPort <IP>:59001 is reachable from the outside. Excellent. Publishing server descriptor. Apr 23 17:57:15.000 [notice] Performing bandwidth self-test...done. Apr 23 23:55:15.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 14 circuits open. I've sent 2.44 MB and received 5.56 MB. I've received 29 connections on IPv4 and 0 on IPv6. I've made 21 connections with IPv4 and 0 with IPv6. Apr 23 23:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 23 23:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 3325179 (server descriptor fetch); 416 (server descriptor upload); 424669 (consensus network-status fetch); 47935 (microdescriptor fetch) Apr 23 23:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 24 05:55:15.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 17 circuits open. I've sent 3.55 MB and received 10.47 MB. I've received 48 connections on IPv4 and 0 on IPv6. I've made 47 connections with IPv4 and 0 with IPv6. Apr 24 05:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 24 05:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 6803210 (server descriptor fetch); 777 (server descriptor upload); 831617 (consensus network-status fetch); 75237 (microdescriptor fetch) Apr 24 05:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 24 11:55:15.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 14 circuits open. I've sent 4.61 MB and received 15.12 MB. I've received 72 connections on IPv4 and 0 on IPv6. I've made 71 connections with IPv4 and 0 with IPv6. Apr 24 11:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 24 11:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 10069221 (server descriptor fetch); 1133 (server descriptor upload); 1260752 (consensus network-status fetch); 94285 (microdescriptor fetch) Apr 24 11:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 1 unique clients. Apr 24 17:55:15.000 [notice] Heartbeat: Tor's uptime is 1 day 0:00 hours, with 15 circuits open. I've sent 5.66 MB and received 19.68 MB. I've received 92 connections on IPv4 and 0 on IPv6. I've made 96 connections with IPv4 and 0 with IPv6. Apr 24 17:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 24 17:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 13235338 (server descriptor fetch); 1513 (server descriptor upload); 1651560 (consensus network-status fetch); 118649 (microdescriptor fetch) Apr 24 17:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 24 23:55:15.000 [notice] Heartbeat: Tor's uptime is 1 day 6:00 hours, with 14 circuits open. I've sent 6.63 MB and received 24.43 MB. I've received 113 connections on IPv4 and 0 on IPv6. I've made 126 connections with IPv4 and 0 with IPv6. Apr 24 23:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 24 23:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 16522259 (server descriptor fetch); 1869 (server descriptor upload); 2065095 (consensus network-status fetch); 151982 (microdescriptor fetch) Apr 24 23:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 25 05:55:15.000 [notice] Heartbeat: Tor's uptime is 1 day 12:00 hours, with 14 circuits open. I've sent 7.61 MB and received 29.17 MB. I've received 128 connections on IPv4 and 0 on IPv6. I've made 151 connections with IPv4 and 0 with IPv6. Apr 25 05:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 25 05:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 19898717 (server descriptor fetch); 2224 (server descriptor upload); 2522039 (consensus network-status fetch); 180939 (microdescriptor fetch) Apr 25 05:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 25 11:55:15.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 14 circuits open. I've sent 8.70 MB and received 33.86 MB. I've received 144 connections on IPv4 and 0 on IPv6. I've made 176 connections with IPv4 and 0 with IPv6. Apr 25 11:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 25 11:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 23131099 (server descriptor fetch); 2581 (server descriptor upload); 2941913 (consensus network-status fetch); 204489 (microdescriptor fetch) Apr 25 11:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 25 17:55:15.000 [notice] Heartbeat: Tor's uptime is 2 days 0:00 hours, with 14 circuits open. I've sent 9.66 MB and received 38.30 MB. I've received 150 connections on IPv4 and 0 on IPv6. I've made 197 connections with IPv4 and 0 with IPv6. Apr 25 17:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 25 17:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 26278426 (server descriptor fetch); 2934 (server descriptor upload); 3313112 (consensus network-status fetch); 221134 (microdescriptor fetch) Apr 25 17:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 25 23:55:15.000 [notice] Heartbeat: Tor's uptime is 2 days 6:00 hours, with 14 circuits open. I've sent 11.02 MB and received 43.50 MB. I've received 164 connections on IPv4 and 0 on IPv6. I've made 219 connections with IPv4 and 0 with IPv6. Apr 25 23:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 25 23:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 29698140 (server descriptor fetch); 3289 (server descriptor upload); 3770948 (consensus network-status fetch); 270111 (microdescriptor fetch) Apr 25 23:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 26 05:55:15.000 [notice] Heartbeat: Tor's uptime is 2 days 12:00 hours, with 14 circuits open. I've sent 12.06 MB and received 48.23 MB. I've received 175 connections on IPv4 and 0 on IPv6. I've made 238 connections with IPv4 and 0 with IPv6. Apr 26 05:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 26 05:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 33051667 (server descriptor fetch); 3644 (server descriptor upload); 4182922 (consensus network-status fetch); 297329 (microdescriptor fetch) Apr 26 05:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 26 11:55:15.000 [notice] Heartbeat: Tor's uptime is 2 days 18:00 hours, with 14 circuits open. I've sent 13.03 MB and received 52.52 MB. I've received 183 connections on IPv4 and 0 on IPv6. I've made 259 connections with IPv4 and 0 with IPv6. Apr 26 11:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 26 11:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 35924906 (server descriptor fetch); 3997 (server descriptor upload); 4585809 (consensus network-status fetch); 320634 (microdescriptor fetch) Apr 26 11:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 26 17:55:15.000 [notice] Heartbeat: Tor's uptime is 3 days 0:00 hours, with 14 circuits open. I've sent 14.14 MB and received 57.94 MB. I've received 227 connections on IPv4 and 0 on IPv6. I've made 286 connections with IPv4 and 0 with IPv6. Apr 26 17:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 26 17:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 39868200 (server descriptor fetch); 4349 (server descriptor upload); 5011550 (consensus network-status fetch); 338988 (microdescriptor fetch) Apr 26 17:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 26 23:55:15.000 [notice] Heartbeat: Tor's uptime is 3 days 6:00 hours, with 14 circuits open. I've sent 15.33 MB and received 62.14 MB. I've received 263 connections on IPv4 and 0 on IPv6. I've made 315 connections with IPv4 and 0 with IPv6. Apr 26 23:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 26 23:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 42672022 (server descriptor fetch); 4710 (server descriptor upload); 5409619 (consensus network-status fetch); 364853 (microdescriptor fetch) Apr 26 23:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 27 05:55:15.000 [notice] Heartbeat: Tor's uptime is 3 days 12:00 hours, with 14 circuits open. I've sent 16.46 MB and received 67.59 MB. I've received 294 connections on IPv4 and 0 on IPv6. I've made 339 connections with IPv4 and 0 with IPv6. Apr 27 05:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 27 05:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 46581059 (server descriptor fetch); 5072 (server descriptor upload); 5916758 (consensus network-status fetch); 396506 (microdescriptor fetch) Apr 27 05:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 27 11:55:15.000 [notice] Heartbeat: Tor's uptime is 3 days 18:00 hours, with 14 circuits open. I've sent 17.40 MB and received 71.76 MB. I've received 327 connections on IPv4 and 0 on IPv6. I've made 361 connections with IPv4 and 0 with IPv6. Apr 27 11:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 27 11:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 49399742 (server descriptor fetch); 5428 (server descriptor upload); 6306806 (consensus network-status fetch); 434479 (microdescriptor fetch) Apr 27 11:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 27 17:55:15.000 [notice] Heartbeat: Tor's uptime is 4 days 0:00 hours, with 14 circuits open. I've sent 18.48 MB and received 76.37 MB. I've received 363 connections on IPv4 and 0 on IPv6. I've made 389 connections with IPv4 and 0 with IPv6. Apr 27 17:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 27 17:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 52642829 (server descriptor fetch); 5783 (server descriptor upload); 6694956 (consensus network-status fetch); 449421 (microdescriptor fetch) Apr 27 17:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 27 23:55:15.000 [notice] Heartbeat: Tor's uptime is 4 days 6:00 hours, with 14 circuits open. I've sent 19.58 MB and received 81.07 MB. I've received 398 connections on IPv4 and 0 on IPv6. I've made 415 connections with IPv4 and 0 with IPv6. Apr 27 23:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 27 23:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 55871065 (server descriptor fetch); 6139 (server descriptor upload); 7099861 (consensus network-status fetch); 472115 (microdescriptor fetch) Apr 27 23:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 28 05:55:15.000 [notice] Heartbeat: Tor's uptime is 4 days 12:00 hours, with 14 circuits open. I've sent 20.86 MB and received 86.85 MB. I've received 437 connections on IPv4 and 0 on IPv6. I've made 453 connections with IPv4 and 0 with IPv6. Apr 28 05:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 28 05:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 59923952 (server descriptor fetch); 6493 (server descriptor upload); 7569990 (consensus network-status fetch); 498710 (microdescriptor fetch) Apr 28 05:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 28 11:55:15.000 [notice] Heartbeat: Tor's uptime is 4 days 18:00 hours, with 14 circuits open. I've sent 21.84 MB and received 91.12 MB. I've received 461 connections on IPv4 and 0 on IPv6. I've made 473 connections with IPv4 and 0 with IPv6. Apr 28 11:55:15.000 [notice] While bootstrapping, fetched this many bytes: 14229 (microdescriptor fetch) Apr 28 11:55:15.000 [notice] While not bootstrapping, fetched this many bytes: 62804633 (server descriptor fetch); 6847 (server descriptor upload); 7979620 (consensus network-status fetch); 518735 (microdescriptor fetch) Apr 28 11:55:15.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Apr 28 12:58:12.000 [notice] Catching signal TERM, exiting cleanly.

2 1

Tor Metrics Search
by Tor Operator 01 May '21

01 May '21

Dear Sirs, Is it time to update? Is boum.tail.org down? Can't find the Tails 4.19 beta to test! -- Regards Tor Operator https://nikulaus.net/tor-operator.html

1 0

Re: [tor-relays] owner of tor log file changes after reboot (patrice)
by Patrice Bönig 26 Apr '21

26 Apr '21

Hi, thanks for your reply. > Are you sure Tor is runnig under user ?pi? and not ?debian-tor?? What > is the value of the ?User? option in torrc? Who is the process owner: > see in `htop`, `top` or similar? Yes. I am starting tor as user pi with: //usr/local/bin/tor --quiet . /Therefore the process is owned by "pi", as htop shows. // There is no specific user specified in the torrc. > Another question is, what?s the reasoning behind switching from a > dedicated user to the default system account??? shared with other services? I only did this, because I could. My thought of this was: Run it as "pi" the main thing is that it is not root. > ? No Raspberry Pi OS Buster here, but googling indicates ?pi? > is the default user on a fresh install. Yes, it is. Why did the owner of the log files changed? Did tor this or the OS? It is solved by setting the user to "pi" in the torrc? regards, Patrice

1 0

OS Upgrade
by kathihil935＠gmail.com 25 Apr '21

25 Apr '21

Ubuntu 20.4 on my Digital Ocean droplet needs to be upgraded. Can the upgrade be done without shutting down the relay. I currently have six flags and don't want to loose them. How is the upgrade done on a relay that is in operation?

8 7

owner of tor log file changes after reboot
by Patrice Bönig 22 Apr '21

22 Apr '21

Hi @all, I have a question and I don't know were I have to look at. I am running a relay (compiled from source) on Raspberry Pi OS Buster. Tor is runs under the user "pi", so the tor logfile has also the user permission (chown pi logfile). Tor starts via crontab (@reboot) but after a reboot the user of the logfile changed to "debian-tor". After every reboot I have to change it back to "pi". Does anyone has an idea what's going on? regards, Patrice

2 1

Questions about consensus votes
by Tobias Höller 22 Apr '21

22 Apr '21

Hi, I have only recently started operating relays (Family:008196DC449482C73CFA9712445223917F760921) and have some trouble with reliably getting the "Fast" and "HSDir" flags for my relays. Right now they regularly obtain and loose these flags and I would like them to be more stable To figure out what was going wrong, I took a look at the archived votes at https://collector.torproject.org/archive/relay-descriptors/votes/ Unfortunately, I still don't understand why some things are happening, so I'm hoping you can help me out: 1. The "Fast" flag is assigned by either measurements (if the DirAuth is also a Bandwidth Auth) or the reported bandwidth. On my relays I noticed that if I set the "BandwidthRate" close to the fast threshold (105KB/s) I would not get the fast flag, unless I configure a much higher bandwidth burst rate (>5MB/s). Even more confusing, different bandwidth auths seem to require different burst rates. While for example Moria1 started voting me fast with a Bandwidth Burst rate of 5Mbit/s, maatuska did not do so until I increased the BandwidthBurst to 100Mbit/s (my complete internet uplink). What I'd like to know: Is that something that only affects me or have you also experienced it? And are there any recommendations how high the bandwidth burst should at least be compared to the desired bandwidth rate? 2. I am confused about the HSDir flag: According to https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2500 it should require the relay to be fast+stable+ uptime>MinUptimeHidServDirectoryV2 (by default 96 hours). So, if an authority votes my relay to be Running+Stable+Fast for 100 consecutive votes, it should vote for "HSDir" in the last 4 votes, right?. Because moria1 for example, votes my relays to be fast+stable+running constantly, but never votes for the HSDir flag. Is there another condition for becoming HSDir that I am not aware of, or can you think of an other reason why this is happening? Lastly, I'd be curious to learn if I am the only operator who has trouble to maintain flags on their relays, or if you have also experienced similar problems to mine. If yes, how did you solve them. kind regards Tobias -- DI Tobias Höller Institute of Networks and Security Johannes Kepler University Linz Altenbergerstraße 69 4040 Linz

3 3

Running a bridge via google cloud
by Keifer Bly 17 Apr '21

17 Apr '21

Hi all, So I am well aware, google cloud is too expensive to run a relay on, but I wonder are they expensive to run a bridge? They are on 1GB eqauls a few cents model. Thank you. --Keifer

1 0

Relay Control
by Kathi 16 Apr '21

16 Apr '21

What actually controls the tor relay? TORRC or nyx? I realize NYX is a 'monitor'. However nyx allows for command line changes; i.e bandwidth/ports etc. thanks

2 1

[RFC] Draft: Expectations for Relay Operators (deadline: May 10, 2021)
by gus 13 Apr '21

13 Apr '21

Dear relay operators, In the last years, during Tor meetups, assemblies, workshops, mailing lists threads, and other gatherings with relay operators, we have discussed topics like relay operational security and good practices, code of conduct, transparency, sustainability, and many more important topics. We believe that it's time and necessary to have an explicit document with these topics to foster and guide good practices in the Tor relay community. This document aims to set some expectations of maintaining the Tor network infrastructure, i.e., Tor relays. To give you an overview of the proposal, it has five topics: 1. Keep users safe 2. Maintain good system op-sec 3. Make sure your relay isn't broken 4. Sustainability 5. Community You can read the draft proposal here: https://gitlab.torproject.org/tpo/community/team/-/wikis/Expectations-for-R… And submit your feedback in this ticket: https://gitlab.torproject.org/tpo/community/relays/-/issues/18 ## Deadline We are opening the document for community consultation and feedback today, April 13, 2021, and you can submit your contribution until May 10, 2021. After closing this public call, we will evaluate and incorporate the relevant feedback into this document's final version. The Expectations for Relay Operators will be published on the Community portal[1] and used to guide our community. ## How to contribute and give feedback After reading the proposal, you can request a GitLab account[2]. If you want to contribute anonymously, you can submit your contribution using Anon-Ticket, which does not require you to create an account. ### Contributing using Anon-Ticket 1. Visit the website: https://anonticket.onionize.space/ 2. Click on "Create Identifier." 3. Save your unique identifier and click on "Login with This Identifier." 4. Select "See a list of all projects" > The Tor Project / Community / Relays > Look for issue #18 > Click on "New Note". 5. Write your feedback and click "Create Note". 6. Finally, a moderator will approve your feedback. Feel free to discuss and reach out to the relays operators community on IRC (irc.oftc.net #tor-relays) or the tor-relays mailing list. Thanks for running relays! Gus ## Notes [1] Community portal Relay Operations: https://community.torproject.org/relay [2] GitLab account creation: https://anonticket.onionize.space/user/gitlab-account/create/ Or https://gitlab.onionize.space/ -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays