- tor-relays - lists.torproject.org

Recent Postings
by manifoil 30 Mar '21

30 Mar '21

Hello fellow Tor Relay operators! Recent activity on this mailing list has given me a headache... Let me explain. I subscribed to this mailing list to keep up to speed with new technical developments, trouble shooting advice and security advisories. If there is a mailing list that covers this criteria, please let me know because that is where I want to be. This recent 'noise' about Mr Stallman is, in my opinion, unnecessary and unwarranted on this particular mailing list. It reminds me of a similar episode on this mailing list a while back where someone appeared to have a personal problem with someone who ran a hosting company - I nearly wrote something about that. My relay has been chugging away at home for many years and bandwidth assigned to the network has steadily increased as my home broadband capability has improved. I am happy that it contributes to Tor and might help people in genuine need - be it politically, racially, sexual orientation wise or as a whistle blower. Finally, I would like to thank the poster who highlighted the OpenSSL vulnerability - my relay was promptly updated. To quote someone else and because I like this persons' sigh-off: With respect, Rattus Norvegicus Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

This past week's most active discussion has forced my hand
by Isaac Grover, Aileron I.T. 30 Mar '21

30 Mar '21

Good morning from Wisconsin, Back in 2019, I was involved in a discussion on this list to seek out hosting providers friendly to Tor exit nodes so that the list on the Tor Project website could be updated and geographic and provider diversity could be improved. Because our twins were newborns at the time, the project took a back burner but I had built up the initial automation and templates for the contacts. Would there be any interest in reviving this project for the aforementioned reasons? 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 2

Tor [0.4.5.7] {Bridge} IPv4 not found
by Someone 30 Mar '21

30 Mar '21

Hey, I'm running Tor [0.4.5.7] on Ubuntu 20.04.2 LTS and started running my first bridge following the exact tutorials on the community guide for running bridge. However, the syslog says(resulting in non-reachability of the port.): Tor[6278]: Unable to find IPv4 address for ORPort 11120. You might want to specify IPv6Only to it or set an explicit address or set Address. Here's my torrc conf: BridgeRelay 1 ORPort 11120 IPv4Only ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:356 IPv4Only ExtORPort auto ContactInfo __REDACTED_FOR_PRIVACY__ Nickname dubridge Steps done: Saw the router configuration (IPv6 disabled in there). Thought maybe some issue with dynamic/static IP so configured DHCP ADDRESS RESERVATION to get a static IP. Followed a similar thread on this topic by a guy recently so wrote IPv4Only in front of both ORPort and obfs4 Thanks! Someone

2 2

Unsubscribing
by Sebastian Urbach 29 Mar '21

29 Mar '21

Dear list, The last days on this list were stunning, to say the least. I'm going to unsubscribe today and i will decide tomorrow if i shut down all my relays. -- Sincerely yours / M.f.G. / Sincères salutations Sebastian Urbach

5 4

My tool I made which makes running relays on Windows very simple.
by Keifer Bly 28 Mar '21

28 Mar '21

Hi all, So this is a tool I developed for tor which makes running relays on Windows very simple. https://www.youtube.com/watch?v=Vpk6yvUWQqU Features: Example torrc file which can be configured as wanted. Automatically checks if tor is running the newest version on startup, if not updates to newest version. One button configuration to configure relay to start when Windows starts. Generates a tor log file which can tell tor messages. Drawbacks: Only supports vanilla bridges. Configures Windows Defender Firewall automatically to allow tor traffic, but other firewalls will need to be manually configured. Cheers. --Keifer

1 0

Reminder: EOL of my 4 tor relays (2 guards, 2 exits).
by Lisa Winter 28 Mar '21

28 Mar '21

Hello people, Lisa here (not my real name, neither is this my e-mail address - it was not stolen however, the owner allows me to use it -, nor is it associated with any of my relays that you could possibly find on the Tor Metrics page). I used to contribute physical resources to the Tor project for a long time now (I don't want to get into too many details, so let's say somewhere between 4 to 7 years) - paying for the co-location of two high-performance dedicated machines , handling nasty abuse reports, you name it.. Anyway each dedicated server was running two Tor instances occccn each single, public IPv4 and IPv6m as this is the maximum AES hardware acceleration was supported by both physical CPU's, so one instance averaged up to 250mbit/s under full load :-D However, I am sick of all the needless communication with my hosting providers, who are well aware of what I am doing with their equipment, yet idiotic jewbie support still spams me with abuse reports, occasionally null-routing entire IP's which was not part of the conract (I have a custom contract co-locating two, older machines).. I am also sick of the Tor staff allowing companies like Team Cymru (short explanation; Team Cymru collects and sells metadata of network connections but not only metadata, also other "valuable" information like zero-day exploits to anyone willing to pay the right price, and much more - they host a bunch of Tor relays and ridges too, which in my opinion should all get the BadExit / similar flag preventing them from being used at all. Tor code development also moves at a snails pace, we still don't have proper patches for circuit exhaustion attack, comparable to HTTP SlowLoris. I will hereby distance myself from the tor project completely, and not come back ever. Please get your shit together @TneTorProject. "Lisa"

1 1

Re: [tor-relays] Unsubscribing
by info＠backplanedns.org 27 Mar '21

27 Mar '21

In the spirit of cancel culture, I will be increasing my exit and guard relay traffic from 100mbps unthrottled pipes to 240. If we are to scrutinize the past actions of every great inventor, thinker, and innovator while disregarding achievements based on personal demerits then there would be no technological advancement. My belief in the mission and purpose still stands. It's about being apart of something bigger than myself or any specific individual regardless of opinion. THAT my friends, should be the consensus weight (pun intended). Dennis Emory Hannon Backplane LLC / BackplaneDNSSent from my T-Mobile 4G LTE device------ Original message------From: Volker MinkDate: Sat, Mar 27, 2021 10:33 AMTo: tor-relays(a)lists.torproject.org;Cc: Subject:Re: [tor-relays] UnsubscribingDont! :/ > Am 27.03.2021 um 15:29 schrieb Sebastian Urbach : > > Dear list, > > The last days on this list were stunning, to say the least. I'm going to unsubscribe today and i will decide tomorrow if i shut down all my relays. > -- > > Sincerely yours / M.f.G. / Sincères salutations > > Sebastian Urbach > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

0.4.6.1-alpha sure is noisy
by Scott Bennett 27 Mar '21

27 Mar '21

Here is the log from today from the heartbeat messages at 9 hours of uptime to the crash messages. Mar 26 16:46:35.356 [notice] Heartbeat: Tor's uptime is 9:00 hours, with 56 circuits open. I've sent 752.71 MB and received 753.05 MB. I've received 5067 connections on IPv4 and 0 on IPv6. I've made 3692 connections with IPv4 and 0 with IPv6. Mar 26 16:46:35.356 [notice] While bootstrapping, fetched this many bytes: 195778 (consensus network-status fetch); 1866820 (microdescriptor fetch) Mar 26 16:46:35.356 [notice] While not bootstrapping, fetched this many bytes: 7043780 (server descriptor fetch); 540 (server descriptor upload); 726053 (consensus network-status fetch); 100992 (microdescriptor fetch) Mar 26 16:46:35.357 [notice] Circuit handshake stats since last time: 20/20 TAP, 1650/1650 NTor. Mar 26 16:46:35.357 [notice] Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 3 v3 connections; initiated 0 and received 384 v4 connections; initiated 3283 and received 4573 v5 connections. Mar 26 16:46:35.357 [notice] DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 same address concurrent connections rejected, 0 connections rejected, 1 single hop clients refused, 0 INTRODUCE2 rejected. Mar 26 16:47:49.441 [notice] Unable to find IPv6 address for ORPort 32323. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 seconds] Mar 26 17:06:38.213 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.307 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.331 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.369 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.418 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.456 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.528 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.553 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.554 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.586 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.614 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.721 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.768 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.831 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.929 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:38.995 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.016 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.079 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.229 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.247 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.315 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.411 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.411 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.411 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.412 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.416 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.416 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.417 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:06:39.418 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.851 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.856 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.856 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.857 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.861 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.861 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.862 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.867 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.867 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.868 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.869 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.869 [warn] tor_bug_occurred_: Bug: src/feature/dircache/consdiffmgr.c:289: cdm_diff_ht_check_and_note_pending: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed. (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.874 [warn] Bug: Tor 0.4.6.1-alpha: Non-fatal assertion ent->cdm_diff_status != CDM_DIFF_PRESENT failed in cdm_diff_ht_check_and_note_pending at src/feature/dircache/consdiffmgr.c:289. Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.874 [warn] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.875 [warn] Bug: 0x1112469 <tor_bug_occurred_+0x1d9> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.875 [warn] Bug: 0x11bf665 <consdiffmgr_rescan+0xa25> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.875 [warn] Bug: 0x1c1baa8c1 <event_base_assert_ok_nolock_+0xa71> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.875 [warn] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.875 [warn] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.876 [warn] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:14:37.876 [warn] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 17:46:35.456 [notice] Heartbeat: Tor's uptime is 10:00 hours, with 54 circuits open. I've sent 805.66 MB and received 805.23 MB. I've received 5696 connections on IPv4 and 0 on IPv6. I've made 4176 connections with IPv4 and 0 with IPv6. Mar 26 17:46:35.457 [notice] While bootstrapping, fetched this many bytes: 195778 (consensus network-status fetch); 1866820 (microdescriptor fetch) Mar 26 17:46:35.457 [notice] While not bootstrapping, fetched this many bytes: 7615013 (server descriptor fetch); 540 (server descriptor upload); 806288 (consensus network-status fetch); 108133 (microdescriptor fetch) Mar 26 17:46:35.457 [notice] Circuit handshake stats since last time: 24/24 TAP, 1696/1696 NTor. Mar 26 17:46:35.458 [notice] Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 3 v3 connections; initiated 0 and received 420 v4 connections; initiated 3732 and received 5165 v5 connections. Mar 26 17:46:35.458 [notice] DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 same address concurrent connections rejected, 0 connections rejected, 1 single hop clients refused, 0 INTRODUCE2 rejected. Mar 26 17:47:49.538 [notice] Unable to find IPv6 address for ORPort 32323. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 seconds] Mar 26 18:10:36.902 [err] tor_assertion_failed_: Bug: src/feature/dirauth/voting_schedule.c:64: create_voting_schedule: Assertion end > start failed; aborting. (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.907 [err] Bug: Tor 0.4.6.1-alpha: Assertion end > start failed in create_voting_schedule at src/feature/dirauth/voting_schedule.c:64: . Stack trace: (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.907 [err] Bug: 0x1106ecc <log_backtrace_impl+0x5c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.907 [err] Bug: 0x1112252 <tor_assertion_failed_+0x142> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.908 [err] Bug: 0x10e8541 <dirauth_sched_recalculate_timing+0x211> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.908 [err] Bug: 0x109b483 <networkstatus_set_current_consensus+0xeb3> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.908 [err] Bug: 0x11d8214 <connection_dir_reached_eof+0x1b74> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.908 [err] Bug: 0x11abc36 <connection_handle_read+0xbe6> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.908 [err] Bug: 0x108f430 <connection_add_impl+0x240> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.909 [err] Bug: 0x1c1baaa8a <event_base_assert_ok_nolock_+0xc3a> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.909 [err] Bug: 0x1c1ba5eec <event_base_loop+0x57c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.909 [err] Bug: 0x109183a <do_main_loop+0x12a> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.909 [err] Bug: 0x108cc6c <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) Mar 26 18:10:36.910 [err] Bug: 0x108b601 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.6.1-alpha ) While it was running, I rebuilt openssl with today's security update and then rebuilt tor. Some hours later the above crash occurred, so the restart should have the patched openssl library running now. I will let the list know if the crash reoccurs. BTW, a message I posted a couple of weeks ago got no responses, so I will ask the most important question again here. What are the new requirements for an HSDir flag? Before last fall, a minimum of 96 or 97 hours of uptime was the only requirements for a relay to be assigned the HSDir flag, but that is clearly not all that is necessary now. 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 * **********************************************************************

1 0

Conduct on this list
by Matthew Finkel 26 Mar '21

26 Mar '21

Please be aware that the Statement of Values [0] and Code of Conduct [1] apply on this mailing list (and all mailing lists provided by the Tor Project). This mailing list started accumulating racist slurs and other insults, which we have held in the moderation queue. Sending a mail containing racist epithets is absolutely not acceptable and will not be tolerated. Racism and sexism are not welcome in this community. Future transgressions will result in the sender being unsubscribed from the mailing lists and reported to the community council. Help us create an open, inclusive, and diverse community supporting Tor's mission. Thanks, Matthew/sysrqb on behalf of the list moderators [0] https://gitweb.torproject.org/community/policies.git/tree/statement_of_valu… [1] https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.t…

1 0

problem with new obfs4 bridge
by Christopher Sheats 26 Mar '21

26 Mar '21

Hello, We’re trying to get a 10GbE dual-stack public obfs4 bridge online, but presumably having some trouble with obfs4. I wished to open a bug, but my request for an account via https://gitlab.onionize.space/ is not being approved. These two recent tickets appear to be related: https://gitlab.torproject.org/tpo/core/tor/-/issues/40311 https://gitlab.torproject.org/tpo/core/tor/-/issues/40107 Ubuntu Server 20.10 tor 0.4.5.7 obfs4proxy 0.8 Firewall accepts TCP/UDP 80/443. Metrics link: https://metrics.torproject.org/rs.html#details/7ADC8C6BF93197830FDF3E06DFB4… torrc: BridgeRelay 1 ORPort 80 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:443 ExtORPort auto ContactInfo tech(a)emeraldonion.org Nickname EmeraldOnionBridge1 MaxMemInQueues 8192MB Log notice file /var/log/tor/notices.log Log notice syslog Tor Browser connect errors: “obfs4 [2620:18c:0:192::194]:443 7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3” 3/26/21, 18:46:55.269 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [2620:18c:0:192::194]:443 ID=H50HNwR2NkpCR9QPST8MdPfmTC43YyZ7sswt9yDTJGA RSA_ID=7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3 ("general SOCKS server failure") “obfs4 [2620:18c:0:192::194]:443” 3/26/21, 18:47:33.467 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [scrubbed] ("general SOCKS server failure") “[2620:18c:0:192::194]” 3/26/21, 19:03:52.905 [WARN] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 2; recommendation warn; host 7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3 at 2620:18c:0:192::194:443) 3/26/21, 19:03:52.905 [WARN] 2 connections have failed: 3/26/21, 19:03:52.905 [WARN] 2 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE “23.129.64.194” 3/26/21, 19:06:43.811 [WARN] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 3; recommendation warn; host 0000000000000000000000000000000000000000 at 23.129.64.194:443) 3/26/21, 19:06:43.811 [WARN] 3 connections have failed: 3/26/21, 19:06:43.811 [WARN] 3 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE No issues: “[2620:18c:0:192::194]:80 7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3” “23.129.64.194:80 7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3” Notices log output: Mar 26 11:38:29.000 [notice] Tor 0.4.5.7 opening log file. Mar 26 11:38:29.600 [notice] We compiled with OpenSSL 1010106f: OpenSSL 1.1.1f 31 Mar 2020 and we are running with OpenSSL 1010106f: 1.1.1f. These two versions should be binary compatible. Mar 26 11:38:29.601 [notice] Tor 0.4.5.7 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1f, Zlib 1.2.11, Liblzma 5.2.4, Libzstd 1.4.5 and Glibc 2.32 as libc. Mar 26 11:38:29.601 [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 26 11:38:29.601 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Mar 26 11:38:29.601 [notice] Read configuration file "/etc/tor/torrc". Mar 26 11:38:29.603 [notice] Opening Socks listener on 127.0.0.1:9050 Mar 26 11:38:29.603 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050 Mar 26 11:38:29.603 [notice] Opening OR listener on 0.0.0.0:80 Mar 26 11:38:29.603 [notice] Opened OR listener connection (ready) on 0.0.0.0:80 Mar 26 11:38:29.603 [notice] Opening OR listener on [::]:80 Mar 26 11:38:29.603 [notice] Opened OR listener connection (ready) on [::]:80 Mar 26 11:38:29.603 [notice] Opening Extended OR listener on 127.0.0.1:0 Mar 26 11:38:29.603 [notice] Extended OR listener listening on port 40739. Mar 26 11:38:29.603 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:40739 Mar 26 11:38:30.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Mar 26 11:38:30.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Mar 26 11:38:30.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 26 11:38:30.000 [notice] Your Tor server's identity key fingerprint is 'EmeraldOnionBridge1 7ADC8C6BF93197830FDF3E06DFB4D96E7CFEDCF3' Mar 26 11:38:30.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'EmeraldOnionBridge1 09E23FA5AD9CF64DBEFE88A39A2F1EB215E44B53' Mar 26 11:38:30.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'EmeraldOnionBridge1 H50HNwR2NkpCR9QPST8MdPfmTC43YyZ7sswt9yDTJGA' Mar 26 11:38:30.000 [notice] Bootstrapped 0% (starting): Starting Mar 26 11:38:36.000 [notice] Starting with guard context "default" Mar 26 11:38:36.000 [notice] Signaled readiness to systemd Mar 26 11:38:36.000 [notice] Registered server transport 'obfs4' at '[::]:443' Mar 26 11:38:37.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Mar 26 11:38:37.000 [notice] Opening Socks listener on /run/tor/socks Mar 26 11:38:37.000 [notice] Opened Socks listener connection (ready) on /run/tor/socks Mar 26 11:38:37.000 [notice] Opening Control listener on /run/tor/control Mar 26 11:38:37.000 [notice] Opened Control listener connection (ready) on /run/tor/control Mar 26 11:38:37.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 26 11:38:37.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 26 11:38:37.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Mar 26 11:38:37.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Mar 26 11:38:37.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Mar 26 11:38:37.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Mar 26 11:38:38.000 [notice] Bootstrapped 100% (done): Done Mar 26 11:38:38.000 [notice] Now checking whether IPv4 ORPort 23.129.64.194:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Mar 26 11:38:38.000 [notice] Now checking whether IPv6 ORPort [2620:18c:0:192::194]:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Mar 26 11:38:39.000 [notice] Self-testing indicates your ORPort [2620:18c:0:192::194]:80 is reachable from the outside. Excellent. Mar 26 11:38:39.000 [notice] Self-testing indicates your ORPort 23.129.64.194:80 is reachable from the outside. Excellent. Publishing server descriptor. Mar 26 11:40:32.000 [notice] Performing bandwidth self-test...done. A prior torrc config set the IPs explicitly, but had the same result: ServerTransportListenAddr obfs4 23.129.64.194:443 ServerTransportListenAddr obfs4 [2620:18c:0:192::194]:443 I can provide debug logs as necessary. Possibly of note, our firewall does not use connection tracking and applies the same rules as our exit relays which use the same ports. Pro-active note: The bridge shares the same 23.129.64.0/24 subnet as Emerald Onion's Tor exit relays, so there is no risk of a user entering and exiting our physical network (see "2.2. Path selection and constraints"): https://github.com/torproject/torspec/blob/master/path-spec.txt Cheers, -- Christopher Sheats Executive Director for Emerald Onion Email: yawnbox(a)emeraldonion.org Phone: +1 206-739-3390 Web: https://emeraldonion.org/

1 0