- tor-relays - lists.torproject.org

Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".
by technonerd＠fea.st 02 Mar '19

02 Mar '19

I run one relay and another tor instance for hidden services and socksport. Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far. Maybe my configs aren't sane? [err] descriptor at 0x8a0acdb0830 begins with unexpected string "". Is another process running in our data directory? Exiting. First config User tor PIDFile /var/run/tor2/tor2.pid SOCKSPort 9052 ControlPort 9053 Log notice file /var/lib/tor2/notices.log RunAsDaemon 1 DataDirectory /var/lib/tor2/data CookieAuthentication 1 ClientUseIPv6 1 ClientPreferIPv6ORPort 1 ClientPreferIPv6DirPort 1 HiddenServiceDir /var/lib/tor2/ssh/ HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/ssh-new/ HiddenServiceVersion 3 HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/bitcoind/ HiddenServicePort 8333 127.0.0.1:8333 Second config User tor PIDFile /var/run/tor/tor.pid Log notice syslog Log notice file /var/log/tor/debug.log #Log notice debug file /var/lib/tor/data/tor.log DataDirectory /var/lib/tor/data ControlPort 9051 HashedControlPassword CookieAuthentication 1 ORPort 9001 ORPort []:9050 DirPort 9030 BandwidthRate 4 MBytes BandwidthBurst 5 MBytes Nickname PancakeWhore ContactInfo ExitPolicy reject *:* ExitPolicy reject6 *:*

5 8

Tor End-of-Life Reminder for tor 0.3.3
by nusenu 02 Mar '19

02 Mar '19

Hi, this is a reminder for everyone still running tor 0.3.3.x. This version reached end of life on 2019-02-28 https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Please keep your relays updated to a version that is still supported. Here is a list affected operators (with cwfr >=0.01) sorted by consensus weight fraction +----------------------------------------------------+---------------------------------------------+------+ | contact | versions | cwfr | +----------------------------------------------------+---------------------------------------------+------+ | abuse(a)to-surf-and-protect.net | 0.3.3.9 | 3.19 | | Servbr Admin <servbr [AT] mail [DOT] md> | 0.3.3.7 | 0.29 | | tor terjan net | 0.3.2.10,0.3.3.7,0.3.3.9 | 0.18 | | florentin aatt rochet ddoott be; LTC: LhRqJZu6U87B | 0.3.3.9 | 0.14 | | Admin <tor(a)ngc292.space> | 0.3.1.9,0.3.2.9 | 0.13 | | tor[at]zeroday.rocks | 0.3.3.9 | 0.12 | | 4096R/61263264 tux3 <barrdetwix(a)gmail.com> | 0.3.3.5-rc | 0.11 | | abuse(a)to-surf-and-protect.de | 0.3.3.9 | 0.11 | | tesuji - 1FZWmNWLrnzGCPPturD3GSiRfHk7vSuSbM | 0.3.0.10 | 0.11 | | Thomas Steen Rasmussen / Tykling <thomas(a)gibfest.d | 0.3.3.7 | 0.11 | | hedonist.jane77(a)tutanota.com | 0.3.3.9 | 0.10 | | Boris Nagaev 19pZzECKDDMbSpaWEy8vGvELEfXM8GrkHS <b | 0.3.2.10 | 0.09 | | contact(a)paulbsd.com | 0.3.2.10 | 0.09 | | 1Q5fZnsG5BSizXmJbrq8FsACnd6kSTBju7 | 0.3.3.7 | 0.08 | | Zwiebel <zwiebel(a)kawo2.rwth-aachen.de> | 0.3.3.9 | 0.08 | | Peter Pan <peterpan(a)fscore.de> | 0.3.2.10 | 0.07 | | Stash Crypto <infrastructure AT stashcrypto dot co | 0.3.1.10 | 0.07 | | DFRI <tor AT dfri dot se> - 1Muz37TfXVBiJKRJkAqTNo | 0.3.3.9 | 0.06 | | Orkan G\u00FCndogdu <orkan95(a)gmail.com> | 0.3.2.10 | 0.06 | | Tor Relay Admin <tor-admin AT meurisse DOT fr> | 0.3.3.9 | 0.06 | | <Mr. Cha Cha> DoTheChaCha(a)protonmail.com | 0.3.3.9 | 0.05 | | drift(a)multinet.no - 1Geq8GGC7qTh7dfptneAYtpeARPAL8 | 0.3.3.9 | 0.05 | | Itzhak Daniel <itzhak+tor(a)itk98.net> | 0.3.1.10 | 0.05 | | Torchwood <contact [at] pakitow [dot] eu> | 0.3.2.10 | 0.05 | | 0x77A31D11 Tony Olagbaiye <frony0 AT gmail dot com | 0.3.0.10 | 0.04 | | 20EE126C6B5C53D48F9D3D21C582B6E15BF059B9 Roman rom | 0.3.3.7 | 0.04 | | 3583217664127336(at)gmail(dot)com [tor-relay.co] | 0.3.3.7 | 0.04 | | Brad Koehn <tor(a)koehn.com> | 0.3.3.8 | 0.04 | | kirtrib(a)gmail.com | 0.3.3.9 | 0.04 | | MaggiWuerze admin(a)maggiwuerze.de | 0.3.1.10 | 0.04 | | Random Person <nobody AT example dot com> | 0.2.5.16,0.3.0.9,0.3.3.7,0.3.3.9 | 0.04 | | seedelmann [you know what belongs here] edelmann [ | 0.3.3.9 | 0.04 | | tor at cybercyber dot wtf | 0.2.5.16 | 0.04 | | Tor Reactor <0d0[AT]protonmail.com> | u42omsvzmh7 | 0.3.3.9 | 0.04 | | tor(a)niij.io | 0.3.3.8 | 0.04 | | torrelay(a)brave.com | 0.3.3.7 | 0.04 | | [ben] <at> [benatherton] <dot> [com] | 0.3.3.9 | 0.04 | | 0x9F29C15D42A8B6F3 Nos oignons <adminsys@nos-oigno | 0.3.3.9 | 0.03 | | 0xA711D81A m_price-at-mit-dot-edu 12fymnTuJsMEgUeR | 0.3.3.9 | 0.03 | | 0xF85959ECB7238802 foertel <mehl(a)foertel.com> | 0.3.3.9 | 0.03 | | 0xFFFFFFFF Random Person <nobody AT example dot co | 0.2.4.29,0.3.2.10,0.3.3.9,0.4.1.0-alpha-dev | 0.03 | | 145tXZyQEfdmpYhmbFtYe84kjghB5ymPA4 swraysford at g | 0.3.3.9 | 0.03 | | 1EpHny(a)protonmail.com - 1EpHnyDUC66N9dMJCyb3Zsc7ws | 0.3.3.9 | 0.03 | | 4096R/0x4cf76925833e2e24 Knight <knight AT germanc | 0.3.3.9 | 0.03 | | 4096R/5819E33F Zhongfu Li <tor at zhongfu dot li> | 0.3.2.10 | 0.03 | | a b u s e. TAT r o t e z e l l e. TOT n e t | 0.3.3.7 | 0.03 | | Alex de Joode <usura(a)sabotage.org> | 0.3.2.9 | 0.03 | | Donate : 1BcGs8GAJwVQ6BpTN9BtRcKvGWzLnmcXwK (UVZCU | 0.3.3.9 | 0.03 | | jim(dot)r(at)outlook(dot)com | 0.3.3.9 | 0.03 | | jimmy(at)bulanik(dot)nl | 0.3.3.7 | 0.03 | | mward44(at)uwo(dot)ca | 0.3.3.9 | 0.03 | | Niccolo <none AT your dot biz> | 0.4.1.0-alpha-dev | 0.03 | | Nicholas Merrill <nick AT calyx dot com> BTC - 14w | 0.2.5.16 | 0.03 | | PhilibertAspert(at)obfuscated(dot)com [tor-relay.c | 0.3.3.6 | 0.03 | | Random Person caceyjones(a)gmail.com | 0.3.2.10 | 0.03 | | sykotik.org US tor node | 0.3.2.10 | 0.03 | | Tor Operator <tor(a)hezmatt.org> | 0.2.5.16 | 0.03 | | tor(at)0day.rocks | 0.3.2.10 | 0.03 | | tor-admin <tor(a)mnesys.org> | 0.3.3.7 | 0.03 | | Torservers.net <support .AT. torservers .DOT. net> | 0.3.2.10 | 0.03 | | 0xB83A02ED Randy Bush <randy AT psg dot com> | 0.3.3.9 | 0.02 | | 0xB9A02A3D Pavol Rusnak <stick+tor(a)gk2.sk> | 0.3.1.8 | 0.02 | | 0xF30A703B Ahh.si abuse <ahh.si+abuse[at]enowaves[ | 0.3.3.9 | 0.02 | | : | 0.3.2.10 | 0.02 | | <hostmaster at denetron dot com> | 0.3.3.9 | 0.02 | | <idabwells AT systemli dot org> | 0.3.3.6 | 0.02 | | <mknoszlig AT zeroton dot in> | 0.3.2.10 | 0.02 | | admin <arbuckletor AT gmail dot com> | 0.3.3.9 | 0.02 | | admin(a)notoriousbit.net | 0.3.3.9 | 0.02 | | Administrator <contact(a)tor-node.net> - BTC 15HkPq8 | 0.2.8.11 | 0.02 | | agata-relay AT jawnosc dot com | 0.3.2.10 | 0.02 | | Alexander Bernhard <alexanderbernhard80 AT gmail d | 0.3.2.10 | 0.02 | | ALEXANDR UVAROV <dbeelial MM gmail.com Nasse-Catte | 0.2.5.16 | 0.02 | | alexkovalev(dot)1990(at)mail(dot)ru [tor-relay.co] | 0.3.3.9 | 0.02 | | calgary2k17(at)gmail(dot)com | 0.3.3.9 | 0.02 | | hannesexner91+tor(a)googlemail.com | 0.2.5.16 | 0.02 | | hoFFy <sebastian @ machinewithoutbrain.de> | 0.3.3.9 | 0.02 | | horst(a)faust-home.de | 0.2.5.16,0.3.2.10 | 0.02 | | isorry(a)no.no | 0.3.2.10 | 0.02 | | Ivanushka Durachok <torstrasse dot leak at spamgou | 0.3.2.10 | 0.02 | | Jon Proulx <jon AT csail dot mit dot edu> GPG Key | 0.3.3.9 | 0.02 | | Kd8hln.com Jeffschefke(a)gmail.com | 0.3.1.9 | 0.02 | | kernelexpl0it(a)jabber.ru | 0.3.2.10 | 0.02 | | madnight madnight <danon(a)gmx.de> | 0.3.1.10 | 0.02 | | Marvin Moloczek <tor(a)moloczek.com> | 0.3.2.10 | 0.02 | | nino [dash] tor [at] ninov [dot] de (gpg B8D657E63 | 0.3.3.7 | 0.02 | | no6gaeda(a)gmail.com | 0.3.3.9 | 0.02 | | none | 0.3.2.10,0.3.3.9 | 0.02 | | Phillip <phillip(a)dangernoodle.de> | 0.3.2.10 | 0.02 | | potlatch protonmail com | 0.3.3.7,0.3.3.9 | 0.02 | | PrisnCell <PrisnCellTor AT tutamail dot com> | 0.3.3.7 | 0.02 | | r.team.hq(a)yandex.ru | 0.3.3.9 | 0.02 | | randm(a)tuta.io | 0.3.2.10 | 0.02 | | RARvolt <rarvolt(a)rarvolt.net> | 0.2.8.12 | 0.02 | | Scott Maxwell tor-contact-2017-beratna (at) scottm | 0.2.5.16 | 0.02 | | ss [aT] xcoin [d0t] ro BTC: bc1q49wsl94gdwpphngpp7 | 0.4.1.0-alpha-dev | 0.02 | | starfleet --at-- trash ..dot.. net | 0.3.3.9 | 0.02 | | suporte(a)wirelesspt.net | 0.3.3.8 | 0.02 | | theshadowghost(a)rambler.ru | 0.3.3.9 | 0.02 | | tor [at] skeeerus [dot] club [tor-relay.co] | 0.3.3.6 | 0.02 | | tor(a)argute.io | 0.3.3.9 | 0.02 | | tor(a)i19.se - 1KN4W7FpzUPURwRQrVGsQCptbR34Kb8n9x | 0.3.3.5-rc | 0.02 | | tormate(at)tuta(dot)io [tor-relay.co] | 0.3.1.9 | 0.02 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2Sezz3DEHDF | 0.3.3.3-alpha | 0.02 | | tor_relay(a)f00bar.wtf | 0.3.2.10 | 0.02 | | ${CONTACT_GPG_FINGERPRINT} ${CONTACT_NAME} ${CONTA | 0.3.1.10,0.3.1.9 | 0.01 | | 0x112CA89F scholzi100 <tor(a)scholzi100.de> 1436DgS4 | 0.3.3.7 | 0.01 | | 0x65714c2b6f3b74cb Thijs Houtenbos <info@thijshout | 0.3.3.9 | 0.01 | | 0xA5CBA13E <tor[AT]d0p1[dot]eu> - 19wzjCe4m6YiiAh | 0.3.2.10 | 0.01 | | 0xB3AC4F40BC396055 Stephan Henrichs <stiepen <twen | 0.3.3.9 | 0.01 | | 59FDAC19FBC4E692652F3EB0C7B7552BDF21283B Smith <qt | 0.3.3.7 | 0.01 | | <548af91b673e7d80d6c9> 9i2c2ranzbol13aif568 at x.o | 0.3.3.6 | 0.01 | | <ben + tor [at] graef . in> 128qLZCaGdoWhBTfaS7ryt | 0.3.3.9 | 0.01 | | <onions at mit dot edu> | 0.3.2.10 | 0.01 | | <pdestor(a)lelantos.org> | 0.3.3.7 | 0.01 | | <tor - chaoshosting . de> | 0.3.1.9 | 0.01 | | <tor AT geekariom dot com> | 0.3.3.9 | 0.01 | | @jbrps 0x588F6C31 <jonas(a)rz-k.de> | 0.3.3.9 | 0.01 | | Admin <admin AT tor-relay dot io> | 0.3.2.10 | 0.01 | | amuse <tor-amuse%foofus.com> | 0.3.2.10 | 0.01 | | Anonymous | 0.2.4.27,0.2.8.12,0.3.2.10 | 0.01 | | Anonymous Coward <anonymous AT nullhost dot net> | 0.3.1.9 | 0.01 | | Antonio Maia <antonio.maia(a)protonmail.com> | 0.3.2.10 | 0.01 | | christianbro <at> yandex <dot> ru - 1D1EjYEGHFPmc8 | 0.2.7.6 | 0.01 | | DeaVulTan <deavultan(a)tuta.io> | 0.2.4.27 | 0.01 | | edgar.tor.uk(a)gmail.com | 0.3.3.6 | 0.01 | | Fabian Schlenz tormaster(a)schle.nz | 0.3.3.7 | 0.01 | | FEC1 B783 BE51 F6E1 DD1B 86C5 A847 5092 E7C3 76AA | 0.3.3.7 | 0.01 | | g <g @ eryd DOT net> | 0.2.4.27 | 0.01 | | human(a)google.com | 0.3.2.10 | 0.01 | | ICOSADEV TOR <icosadev(a)gmail.com> | 0.3.0.9 | 0.01 | | Inbox: tor/sevenlayers/org | 0.3.2.10 | 0.01 | | inbox(a)wooodoka.ru | 0.2.6.10 | 0.01 | | Kristofer Hallin mail(a)krihal.se | 0.3.3.7 | 0.01 | | lagartobostero(a)hotmail.com | 0.3.3.7 | 0.01 | | Me <wiz.ard(a)gmx.net> | 0.3.3.7 | 0.01 | | Meet me on the balcony | 0.3.3.6 | 0.01 | | Micah Sherr <msherr(a)cs.georgetown.edu> | 0.3.2.9-dev | 0.01 | | mshepard2(a)maricopa.edu | 0.3.2.10 | 0.01 | | Nick Sheppard <nicksheppard03(a)gmail.com> | 0.2.7.6 | 0.01 | | ohello(a)tuta.io | 0.3.0.13 | 0.01 | | Person d(a)mdng.me | 0.2.5.12 | 0.01 | | PGK <tor at the-goober.net> | 0.3.3.9 | 0.01 | | Pierre <pierre+tor at ratni dot v4v dot be> | 0.3.3.7 | 0.01 | | Random Person <periplanetaamericanus AT gmail dot | 0.3.3.9 | 0.01 | | Random Person <tor at 1d4 dot us> - 1N7sBLKvekRD4E | 0.3.3.6 | 0.01 | | Random Person tort(a)pike.pl | 0.3.1.9 | 0.01 | | Ranlvor <tor AT starletp9 dot de> | 0.3.3.9 | 0.01 | | rhfred(a)disroot.org | 0.3.2.10 | 0.01 | | Rogemedic <admin(a)waltersnet.noip.us> | 0.3.2.10 | 0.01 | | shallot protonmail com | 0.3.3.3-alpha | 0.01 | | support @ TORdashRELAYdotUS | 0.3.2.10 | 0.01 | | Sysadmin of the Day Role Person <wbb aaaaattttt fa | 0.3.2.10 | 0.01 | | TC <thinkcolorful AT thinkcolorful dot org> | 0.3.3.9 | 0.01 | | Tobias Meggendorfer Mail:<tobias .AT. meggendorfer | 0.3.2.10 | 0.01 | | tor(a)alexdpsg.net | 0.3.3.9 | 0.01 | | tor(a)haltmayer.com | 0.3.3.9 | 0.01 | | tor(a)remus.be | 0.3.3.8 | 0.01 | | twink0r @ twitter | 0.3.3.7 | 0.01 | | was.small(a)was.info | 0.3.3.9 | 0.01 | | Wubim Foundation <services AT wubim DOT com> | 0.3.1.9 | 0.01 | | Wubim Foundation <services AT wubim.com> | 0.3.3.9 | 0.01 | +----------------------------------------------------+---------------------------------------------+------+ -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Debugging ipv6 conenctivity
by Charly Ghislain 25 Feb '19

25 Feb '19

Hi all, My tor relay has got the UnreachableIpv6 flag set once i mentionned an OrPort with my ipv6 address. >From what i can tell, my server is reachable over ipv6, and can contact the directory authorities through ipv6 (following the instructions found there: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Makesurerelaypo… ). The node is behind an haproxy that relays ipv6 traffic to natted ipv4 (with no logging for those concerned). It seems to work fine for web content over ipv6, and traffic on both ips (v4 and v6) goes through this channel. I can successfully telnet my node ORPort using my v6 address. The ports have been defined this way in torrc: ORPort 0.0.0.0:9001 NoAdvertise ORPort 91.121.79.188:9001 NoListen ORPort [2001:41d0:1:84bc::1]:9001 NoListen Is there a way to make a tor client connect to a specific relay to debug this kind of connectivity issues? Or any other mean? In the meantime ive removed the advertized ip6. Regards, Charly

4 6

Regarding linux-tor-prio.sh script
by rl1987＠sdf.lonestar.org 24 Feb '19

24 Feb '19

Hello, Tor repository contains the following script, that has not been updated much in last 10 years or so: https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor… Do people still use? Is it safe to remove it from the repo? Regards

1 0

Memory Used dropped again with 0.3.5.8
by petrarca＠protonmail.ch 24 Feb '19

24 Feb '19

Just an fyi for those who might be interested... With upgrading to 0.3.5.8 the memory usage of my Tor relay dropped again to reasonable levels. It suddenly started to increase end of January causing my relay to crash twice before leveling around 45% (a week before I had an ISP outage). Now it's back to around 25%. The relay bandwidth consumed over all the time was pretty much stable. [Memory Used.png]

1 0

relayor v19.0.0 is released
by nusenu 23 Feb '19

23 Feb '19

Hi, relayor has been made for relay operators to help them install and manage tor relays with minimal effort. https://github.com/nusenu/ansible-relayor Changes since v18.1.1 ------------------------------ - torrc: enable tor's Sandbox feature by default on Ubuntu (where it was previously disabled as a workaround for #160 ) don't set tor RelayBandwidthBurst if the input field is empty - increase tor_alpha_version 0.3.4.x -> 0.4.0.x - increase min ansible version 2.6.2 -> 2.7.8 - add support for OpenBSD 6.4 - add support for FreeBSD 12 (drop 10.x) - README: mark CentOS/Fedora as currently broken due to upstream package issues #185 - test-kitchen: add OpenBSD support add guard-alpha test-suite kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

How To Add Reachable Ports To OBFS4 Bridge
by Keifer Bly 22 Feb '19

22 Feb '19

Hi all, So I am looking to add some reachable ports to my OBFS4 bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E CF14E5B9E9A As this list is public, I guess I should not provide the port numbers that tor and obfs4 are running on. However, would adding reachable ports like 80, 443, 8080 be doable? I know that these ports that might not bind very well as lots of other types of traffic use them, however I saw the ticket at https://trac.torproject.org/projects/tor/ticket/7875 And this raises a concern about bridges being reachable for users who are connecting from behind firewalls, etc (hence the reason why they need to use a bridge), it seems like a good idea to have bridges reachable on ports that aren't likely to be blocked by network administrators or ISPS. Let me know what you think. --Keifer

2 2

Relay operators meetup Lisbon (23.02.2019)
by Vasilis 22 Feb '19

22 Feb '19

Dear Tor friends and relay operators, Tomorrow (23.02.2019) a relay operators meetup will take place at Block cafe, Berlin. When: Saturday, February 23rd, 2019 Time: 15:00 / 3:00 PM Where: Block Cafe, Rua Latino Coelho 63, 1st floor, 1050-133, Lisbon, Portugal Event link: https://privacylx.org/en/events/tormeetup3/ Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Neel Chauhan 19 Feb '19

19 Feb '19

Hi tor-relays@ mailing list, I have a Tor relay "NeelTorRelay2": https://metrics.torproject.org/rs.html#details/D5B8C38539C509380767D4DE20DE… This relay is hosted on a 300 mbps Verizon FiOS (FTTH/GPON) connection. My server is a HPE ProLiant MicroServer Gen10 (quad-core AMD X3421 variant) running FreeBSD, and my router is a Linksys WRT1900AC running OpenWrt. For some reason, the Advertised Bandwidth is not going above ~19.5 MiB/s. If my relay is pushing 10MB/s (80mbps) at a given time, the CPU usage is around 20%, so I don't think its the CPU. My question is that is this lower Advertised Bandwidth speeds normal for a relay hosted on a connection behind a consumer level router and it's NAT table (even despite OpenWrt)? Could it be Verizon's DPI/QoS now that Net Neutrality is repealed? Would using a non-consumer router (like Ubiquiti or pfSense) help? Thank You, Neel Chauhan === https://www.neelc.org/

4 4

Re: [tor-relays] Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by starlight.2018q2＠binnacle.cx 18 Feb '19

18 Feb '19

Neel Chauhan neel at neelc.org at Mon Feb 18 18:05:47 UTC 2019 > >I feel it's my Linksys WRT1900AC because consumer routers aren't >designed for the traffic high-bandwidth Tor relays handle, even after >flashing things like OpenWrt. The router is probably dropping packets and is problem. Also consumer grade switches generally cannot handle FiOS without dropping tons of packets. A one TCP connection speedtest will not trigger overload the way a 7000 connection Tor router does. Dealt with this here by attaching the Linux server directly to FiOS and having it act as the outside router. The relay would run much better but I fried the mainboard with a PCIx NIC overload; swapped in an incredibly ancient system formerly collecting dust on a shelf. Too busy/lazy to put up the newer box waiting to take it's place.

1 0

Re: [tor-relays] Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Roman Mamedov 18 Feb '19

18 Feb '19

On Mon, 18 Feb 2019 09:06:05 -0500 Neel Chauhan <neel(a)neelc.org> wrote: > Verizon gives both 300 mbps upload and download speeds. Uploads are more > heavily oversubscribed on FiOS, primarily because GPON gives 2.5gbps > downloads and 1.25gbps uploads. But then again the upload will be barely utilized by typical residential Internet users. Still my recommendation is to test your bandwidth in multiple ways first, be it speedtest.net, or (better yet) https://github.com/sivel/speedtest-cli, or iperf3 servers, if you can find any near your location. If tests show that you do get near 300 Mbit both directions, the next step would be to just set up two instances of Tor, as I suggested before in your thread[1]. Actually fun to see my prediction from back then coming true precisely (with regard to getting only 200 Mbit). [1] https://www.mail-archive.com/tor-relays@lists.torproject.org/msg15819.html Running two instances is the universal solution which should improve Tor's bandwidth utilization on almost any connection. -- With respect, Roman

2 2

IRC operator meeting - February 7th
by Colin Childs 13 Feb '19

13 Feb '19

Hi everyone, As previously discussed (https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html <https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html>) we are resuming our IRC relay operator meetings this Thursday, February 7th @ 2:00UTC. These meetings will be held in #tor-meeting on irc.oftc.net <http://irc.oftc.net/>. If you’d like to add to the agenda, please edit the pad at https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D… <https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D…> See you all there!

2 3

Re: [tor-relays] BadExit why?
by Olaf Grimm 12 Feb '19

12 Feb '19

Thank you for the answer. I try to get a new IP from the Trabia support. Olaf Am 12.02.19 um 21:51 schrieb David Goulet: > On 12 Feb (21:35:29), Olaf Grimm wrote: >> inet 178.175.148.15 > Thanks Olaf! > > That IP was flagged as rewritting bitcoin addresses on Jan 21st, 2019. > > It appears you re-used a malicious IP from I.C.S. Trabia-Network S.R.L. > > Do you have an easy way to request a new IP for that Exit node or it is kind > of a pain? > > Un-blacklisting a relay that is still not considered expired from our reject > rule set can be a laborious process because essentially, we have to make a > case to the directory authorities and they decide if they remove the rule or > not based on our arguments ;). > > So changing the IP would be definitely the easiest way else we can try to > convince the dirauth :). > > Sorry for the inconvenience! > David > >> Am 12.02.19 um 21:34 schrieb David Goulet: >>> On 12 Feb (21:30:10), Olaf Grimm wrote: >>>> Hello ! >>>> >>>> I provisioning a new exit since two hours. It is a totally new relay in >>>> a VM. My other relays at the same provider are ok. Why I see "BadExit" >>>> in Nyx??? Now my first bad experience with my 11 relays... >>>> >>>> fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD >>>> Nickname Hydra10 >>> This relay is not yet on Relay Search: >>> >>> http://rougmnvswfsmd4dq.onion/rs.html#search/CCDC4A28392C7448A34E98DF872213… >>> >>> I'm guessing it is quite new. >>> >>> That fingerprint is *not* set as a BadExit so this means you might have gotten >>> the IP address of an old BadExit. >>> >>> Can you share the address so I can look it up? >>> >>> Thanks! >>> David >>> >>>> At all exits I have the same firewall rules and torrc configs: >>>> >>>> ufw status >>>> Status: active >>>> >>>> To Action From >>>> -- ------ ---- >>>> 22/tcp ALLOW Anywhere >>>> 9001/tcp ALLOW Anywhere >>>> 9030/tcp ALLOW Anywhere >>>> 80/tcp ALLOW Anywhere >>>> 443/tcp ALLOW Anywhere >>>> 1194/tcp ALLOW Anywhere >>>> 53/tcp ALLOW Anywhere >>>> 53/udp ALLOW Anywhere >>>> 1194/udp ALLOW Anywhere >>>> 22/tcp (v6) ALLOW Anywhere (v6) >>>> 9001/tcp (v6) ALLOW Anywhere (v6) >>>> 9030/tcp (v6) ALLOW Anywhere (v6) >>>> 80/tcp (v6) ALLOW Anywhere (v6) >>>> 443/tcp (v6) ALLOW Anywhere (v6) >>>> 1194/tcp (v6) ALLOW Anywhere (v6) >>>> 53/tcp (v6) ALLOW Anywhere (v6) >>>> 53/udp (v6) ALLOW Anywhere (v6) >>>> 1194/udp (v6) ALLOW Anywhere (v6) >>>> >>>> Please take a look what happens. >>>> >>>> Olaf >>>> _______________________________________________ >>>> 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 > > >

2 1

BadExit why?
by Olaf Grimm 12 Feb '19

12 Feb '19

Hello ! I provisioning a new exit since two hours. It is a totally new relay in a VM. My other relays at the same provider are ok. Why I see "BadExit" in Nyx??? Now my first bad experience with my 11 relays... fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD Nickname Hydra10 At all exits I have the same firewall rules and torrc configs: ufw status Status: active To Action From -- ------ ---- 22/tcp ALLOW Anywhere 9001/tcp ALLOW Anywhere 9030/tcp ALLOW Anywhere 80/tcp ALLOW Anywhere 443/tcp ALLOW Anywhere 1194/tcp ALLOW Anywhere 53/tcp ALLOW Anywhere 53/udp ALLOW Anywhere 1194/udp ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 9001/tcp (v6) ALLOW Anywhere (v6) 9030/tcp (v6) ALLOW Anywhere (v6) 80/tcp (v6) ALLOW Anywhere (v6) 443/tcp (v6) ALLOW Anywhere (v6) 1194/tcp (v6) ALLOW Anywhere (v6) 53/tcp (v6) ALLOW Anywhere (v6) 53/udp (v6) ALLOW Anywhere (v6) 1194/udp (v6) ALLOW Anywhere (v6) Please take a look what happens. Olaf

3 2

plans to require ContactInfo to be non-empty
by nusenu 11 Feb '19

11 Feb '19

Hi, due to some recent and ongoing events related to a malicious entity running tor relays I'll start to pursue an idea that I had for some time: require non-empty ContactInfo (non-empty does not mean valid email address) This is primarily a non-technical policy discussion which will take place on tor-dev@. If you want to help right away and currently don't make use of the ContactInfo, please set it. If you think such a change would negatively affect you please let me know (off-list is also fine if you prefer). thanks, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

9 12

2 ip addresses at the same device, works except for the DirPort
by Toralf Förster 07 Feb '19

07 Feb '19

I ordered a 2nd ip address for my server and put them in the first order in my network configuration. I do wonder, why this adapted torrcconfiguration: $> cat /etc/tor/torrc # torrc at tor-relay # PIDFile /var/run/tor/tor.pid DataDirectory /var/lib/tor/data Nickname zwiebeltoralf OutboundBindAddress 5.9.158.75 DirPort 80 ORPort 443 DirPort [2a01:4f8:190:514a::2]:80 NoAdvertise ORPort [2a01:4f8:190:514a::2]:443 ControlPort 9051 Log warn file /tmp/warn.log #Log notice file /tmp/notice.log #Log info file /tmp/info.log ExitRelay 0 IPv6Exit 0 works at the first glance (about 6,000 connection) but still give after a while in the log: Feb 06 19:59:08.000 [notice] Tor 0.4.0.1-alpha opening log file. Feb 06 20:19:26.000 [warn] Your server (<xx>:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. (where <xx> is the new main ip address at my eth0 device) -- Toralf PGP C4EACDDE 0076E94E

2 2

Tor meetup @ Onionspace, Berlin
by Vasilis 03 Feb '19

03 Feb '19

Dear Tor friends and relay operators, Tomorrow (02.02.2019) a relay operators meetup will take place at Onionspace, Berlin. When: Saturday, February 2nd, 2019 Time: 16:00 / 4:00 PM Where: Gottschedstrasse 4, Entrance 4, 13357 Berlin (U Nauener Platz) Event link: https://blog.torproject.org/events/tor-meetup-berlin Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

3 2

note to Falback Directory operators: bandwidth wasting bot
by starlight.2018q2＠binnacle.cx 03 Feb '19

03 Feb '19

For the last year a bot of some kind has loaded Fallback Directory relays with excessive directory document requests. Some detail can be found in ticket #27921 at https://trac.torproject.org/projects/tor/ticket/27921. To determine if your relay is affected, look the relay up in https://metrics.torproject.org/rs.html, click the 6-Month history tab, and examine the graph for significantly higher "write bytes per second" relative to "read bytes per second". I find this annoying (since I pay for the wasted bandwidth) and came up with a one-line hack that mitigates the abuse without impairing the usefulness of the DIR service to normal relays and clients. If you compile your daemon from source and are interested contact me directly for the patch.

2 1

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits
by petrarca＠protonmail.ch 03 Feb '19

03 Feb '19

There is something really strange going on indeed. What I noticed is an increase of circuits and my device running out of memory until it stopped working so I had to reboot it on 31. Jan. Then again the memory usage increased until it leveled out at a rather unusual, high usage. The actual bandwidth usage is not unusual though (always around 2Mbps on my relay). Attached a screenshot of my memory usage the last few days (I hope attachments do work here; it's in fact Tor using that memory as could be checked with ps and htop). Heartbeat messages of the log are: Jan 31 10:57:56.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 447 circuits open. I've sent 2.66 GB and received 2.65 GB. Jan 31 16:57:56.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 19764 circuits open. I've sent 9.59 GB and received 9.54 GB. Jan 31 22:57:56.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 54178 circuits open. I've sent 12.36 GB and received 12.30 GB. Feb 01 04:57:56.000 [notice] Heartbeat: Tor's uptime is 23:50 hours, with 79333 circuits open. I've sent 14.89 GB and received 14.81 GB. Feb 01 10:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 5:50 hours, with 110815 circuits open. I've sent 19.55 GB and received 19.45 GB. Feb 01 16:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 11:50 hours, with 141724 circuits open. I've sent 24.03 GB and received 23.90 GB. Feb 01 22:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 17:50 hours, with 12829 circuits open. I've sent 29.96 GB and received 29.75 GB. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 1. February 2019 23:50, Roman Mamedov <rm(a)romanrm.net> wrote: > Hello, > > There seems to be an issue with Tor's memory usage. > Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the > machine got 430 MB into swap, slowing down to a crawl from iowait on accessing > the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" > in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that > doesn't add up to exhausting the 1.5 GB, and there are no other heavy > processes on the machine running. I rebooted it without further investigation. > > And right now on another machine running 2.9.16 I see: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor > > But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up > recently. > > Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, > with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. > Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: > 11361/11361 TAP, 239752/239752 NTor. > Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; > and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, > and 8779474 v4 connections. > Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits > rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. > Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) > failed. > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > With respect, > Roman > > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4 3

FOSDEM Relay Operator Meetup
by relaya relaya 02 Feb '19

02 Feb '19

Hello! I read there is a Relay Operator Meetup organized by Colin at. I'm surprised it has not been announced on this list yet. Where and when does it take place exactly? thank you!

2 3

AS: "I.C.S. Trabia-Network S.R.L."
by nusenu 02 Feb '19

02 Feb '19

Hello, if you are the operator of the relays listed bellow, please set MyFamily and contactInfo in your torrc to avoid getting rejected. ornetradar(a)riseup.net: > 2019-02-01 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+-----------------+------+-------+--------+-----------+---------------------------+--------------+---------------+------------------------------------------| > | 1 | 1 | 13:41:51 | 178.175.132.211 | md | 9001 | 8080 | 0.3.5.7 | chatter | chatter | 1 | E0259C34CEDF2D7A15271336EF65E21171EDF0FE | > | 1 | 1 | 13:44:58 | 178.175.132.210 | md | 9001 | 8080 | 0.3.5.7 | rendon | rendon | 1 | 14678AB26ED87E843B232EAEDF2A7BB384652473 | > | 1 | 1 | 13:44:58 | 178.175.143.158 | md | 9001 | 8080 | 0.3.5.7 | lincoln | lincoln | 1 | 56F55271722E2F8FFC3A77CA3F7F955B703CB027 | > | 1 | 1 | 13:44:59 | 178.175.132.212 | md | 9001 | 8080 | 0.3.5.7 | dossier | dossier | 1 | 1B2E31990B0F0A51920F40D5AB7598D41B214A20 | > | 1 | 1 | 13:44:59 | 178.175.132.213 | md | 9001 | 8080 | 0.3.5.7 | lark | lark | 1 | 1C3EE6E25868F0A8B816B62D81534146F2616008 | > | 1 | 1 | 13:44:59 | 178.175.143.156 | md | 9001 | 8080 | 0.3.5.7 | cuban | cuban | 1 | 1F25B74EF811858112DE18220B456F3CF6EE642E | > | 1 | 1 | 13:44:59 | 178.175.143.157 | md | 9001 | 8080 | 0.3.5.7 | charly | charly | 1 | 3722EEBB445B4E91B1A10CED86CD2E32B3C92D41 | > | 1 | 1 | 13:44:59 | 178.175.132.209 | md | 9001 | 8080 | 0.3.5.7 | matador | matador | 1 | 3E48BE2E2AC257D20546B5547729F4A5096BE39F | > | 1 | 1 | 13:44:59 | 178.175.132.214 | md | 9001 | 8080 | 0.3.5.7 | azorian | azorian | 1 | 72193825EE4EE6F9EF3243D8A7B49DB9122ADF21 | > | 1 | 1 | 13:44:59 | 178.175.143.155 | md | 9001 | 8080 | 0.3.5.7 | contras | contras | 1 | A67EB8AA880ACC94B716E178576142CB25D63B8C | > > https://nusenu.github.io/OrNetRadar/2019/02/01/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Circuit storms
by starlight.2018q2＠binnacle.cx 01 Feb '19

01 Feb '19

Jan 26 Heartbeat: circuits 6666 sent 103gb received 100gb Jan 26 Heartbeat: circuits 5672 sent 101gb received 98gb Jan 26 Heartbeat: circuits 6156 sent 106gb received 103gb Jan 26 Heartbeat: circuits 5902 sent 92gb received 90gb Jan 27 Heartbeat: circuits 6171 sent 80gb received 78gb Jan 27 Heartbeat: circuits 5920 sent 85gb received 82gb Jan 27 Heartbeat: circuits 4841 sent 82gb received 79gb Jan 27 Heartbeat: circuits 5718 sent 77gb received 71gb Jan 28 Heartbeat: circuits 5676 sent 86gb received 80gb Jan 28 Heartbeat: circuits 5157 sent 84gb received 81gb Jan 28 Heartbeat: circuits 7548 sent 105gb received 102gb Jan 28 Heartbeat: circuits 16448 sent 88gb received 84gb Jan 29 Heartbeat: circuits 31521 sent 107gb received 97gb Jan 29 Heartbeat: circuits 6255 sent 90gb received 86gb Jan 29 Heartbeat: circuits 14920 sent 91gb received 89gb Jan 29 Heartbeat: circuits 21502 sent 75gb received 72gb Jan 30 Heartbeat: circuits 37649 sent 80gb received 76gb Jan 30 Heartbeat: circuits 69831 sent 84gb received 81gb Jan 30 Heartbeat: circuits 16740 sent 102gb received 99gb Jan 30 Heartbeat: circuits 59552 sent 105gb received 101gb Jan 31 Heartbeat: circuits 73727 sent 88gb received 84gb Jan 31 Heartbeat: circuits 12156 sent 74gb received 71gb Jan 31 Heartbeat: circuits 63624 sent 81gb received 79gb Jan 31 Heartbeat: circuits 89129 sent 77gb received 72gb Feb 1 Heartbeat: circuits 98432 sent 105gb received 80gb Feb 1 Heartbeat: circuits 97975 sent 69gb received 66gb Feb 1 Heartbeat: circuits 27443 sent 94gb received 91gb

1 0

Tor RAM usage (DoS or memory leaks?)
by Roman Mamedov 01 Feb '19

01 Feb '19

Hello, There seems to be an issue with Tor's memory usage. Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the machine got 430 MB into swap, slowing down to a crawl from iowait on accessing the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that doesn't add up to exhausting the 1.5 GB, and there are no other heavy processes on the machine running. I rebooted it without further investigation. And right now on another machine running 2.9.16 I see: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up recently. Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: 11361/11361 TAP, 239752/239752 NTor. Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, and 8779474 v4 connections. Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) failed. -- With respect, Roman

1 0

tor relay shutsdown
by Neelix 01 Feb '19

01 Feb '19

Hello, I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen? Regards, Neelix fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E

5 11

Circuit storms
by Felix 31 Jan '19

31 Jan '19

Hi everybody Circuit storms observed of up to 100k and 250k per relay for over hours. Consumed BW rises by about 10%. Number of stateful server connections is higher. Using Tor 356 to 401. Anybody else observes that? Switching to some paranoid server settings for some days :) -- Cheers, Felix

2 2

Installing Tor As Windows Service And Updating Via Script (was RE: Having Trouble With Speed Of OBFS4 Bridge)
by Keifer Bly 30 Jan '19

30 Jan '19

Darn, I just restarted the relay because tor 0.3.5.7 came out today before seeing this email. I have been playing with the Windows Powershell regarding this and made some interesting discoveries. So, I found that the Windows Powershell equivalent to linux's "apt-get" is "install-package -Name". And so, I tried running "install-package -name tor" and got this error (see the attached screenshot). The error is that tor project is not in the list for Windows to install packages from on Windows (it's not finding tor packages as a result), as I discovered at the other attached image. However, according to my research at https://docs.microsoft.com/en-us/powershell/module/packagemanagement/regist… Windows Powershell can register sources to install packages from via Register-PackageSource -Name command listed. So Something along the lines of PS C:\> Register-PackageSource -Name "tor" -Location "http://torurl" -ProviderName "TorProject" may have interesting results possibly. What is the tor packages download url so I may try this? Once this is returned to me I will return to the list with my findings. Cheers. -----Original Message----- From: tor-relays <tor-relays-bounces(a)lists.torproject.org> On Behalf Of teor Sent: Monday, January 28, 2019 10:24 PM To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] Having Trouble With Speed Of OBFS4 Bridge On January 29, 2019 3:45:55 AM UTC, Keifer Bly <keifer.bly(a)gmail.com> wrote: >Thanks. I also wanted to ask, is there a way to upgrade tor using >Windows Powershell? The way I am doing that is downloading the tor >expert bundle when a new one is released and manually replacing both >tor.exe and obfs4.exe with the new versions. I have tor installed as a >Windows service via powershell, so is there a way to do this? I am >asking because the current tor expert bundle is tor 0.3.4.8 whereas I >believe 0.3.5.7 has been released. Thank you. Hmm, I thought someone answered this question already, but I can't find the answer in the list archives. 0.3.4.8 is still a supported version. You don't need to update. One simple way to keep Tor up to date on Windows is to use the Chocolatey package manager to install the tor package: https://chocolatey.org/packages/tor It has Tor 0.3.3.9, which is still a recommended version. You can script chocolately using the "choco" command. Otherwise, you can script powershell to download and install packages. I can't help you with the details, because I don't do a lot of work on Windows. But maybe someone else on the list can. If you work out how to do it, please write back to the list with the scripts you used. T -- teor ---------------------------------------------------------------------- _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

IRC relay operator meetups
by Colin Childs 29 Jan '19

29 Jan '19

Hi everyone, The IRC Tor relay operator meetups are beginning again! To get started, we are going to be holding these meetups once per month. The meetups will be held the first Thursday of the month, at 2:00UTC. This means the February meetup will be held next week, on the 7th. To allow us to use meetbot for recording the meetup, we will be holding them in #tor-meeting. On the first Monday of the month, I will send out a reminder email with the date and time, along with a pad that people can add discussion topics to. For February, the reminder email will go out on the 4th. I look forward to seeing everyone there!

1 0

Hetzner - "no.spam@example.com" relays
by nusenu 29 Jan '19

29 Jan '19

Hi, to the operator of the relays listed bellow. You care currently not setting the MyFamily option on your relays, which puts tor users at risk. Please configure your relays with MyFamily to avoid getting your relays rejected. more information: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#Whatis… 2019-01-28 | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+---------------------+-----------+----------------+---------------------+------+-------+--------+-------+---------------------+---------------+------------------------------------------| | 0 | 0 | 01:34:19 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 24C3BC672621D6FCB7923DE031738B23EE0C1819 | | 0 | 0 | 01:48:53 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CBDCA8B16E2D4111A6618BAB3F114C358B8E35DB | | 1 | 0 | 05:00:50 | somerelay1IHcuer9Cn | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CA307A53194D6DE8B033226C541654117AFCF5F2 | | 1 | 0 | 02:54:44 | somerelayId8wPoBbRJ | 0.3.3.7 | 116.203.57.160 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | F9578C192A76062C2B49F938A53291AA5CE3CFBF | | 1 | 0 | 02:54:49 | somerelayT7WbYRznBW | 0.3.3.7 | 116.203.59.81 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CFDF026F3FC52BF347A395A1224D70D9ACBEF9C5 | | 1 | 0 | 02:55:45 | somerelayung2AiqzXu | 0.3.3.7 | 116.203.66.45 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 97F47C07A3DEA4C1A885C2C15008592635DA54B6 | | 1 | 0 | 02:54:46 | somerelayvpoDStFnGZ | 0.3.3.7 | 94.130.184.189 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 5CD0F83B59229F86419757FE54CFF6EE859EA0ED | https://nusenu.github.io/OrNetRadar/2019/01/28/a7 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Having Trouble With Speed Of OBFS4 Bridge
by Keifer Bly 29 Jan '19

29 Jan '19

Hello, So my OBFS4 bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E CF14E5B9E9A seems to be having some speed issues, only reaching about 40-50 kb/s of speed. This is strange, as it should be much faster than this. My thoughts on why this is happening: Where I living, am probably nowhere near the bridge authorities for one. I am running an obfuscated bridge (which as this requires an additional process to be running alongside the tor process, could this be a part of it?) I am running off of the only internet provider available in my area (Charter / Spectrum) which is an isp that uses cable structure so maybe they have some kind of limitation in place? My router is a Netgear Orbi router which should be able to handle up to 60,000 connections at once so there should be no issue there. Any help is appreciated, thank you. --Keifer

3 8

diff-cache OOM
by notatorserver 28 Jan '19

28 Jan '19

I am running tor 4.0.1-alpha inside a docker container with a memory limit (6GB). Tor runs out of memory and aborts or crashes periodically. Usually I see an error message like this: Could not mmap file "/var/lib/tor/data/diff-cache/1149": Out of memory ...(repeated some number of times) followed by segfault Sometimes I see a message: Out of memory on malloc(). Dying followed by abort. Am I correct to assume the diff-cache is the issue here? Looking at the files it seems they are all pretty small (~500K). Is some badly behaved client requesting 12,000 of these diffs causing my relay to mmap them all at once? or is it just expensive to generate and generating 30-60 at once is enough to use all the memory? Are there any config options to reject expensive queries or otherwise limit concurrency? Thanks

2 2

Shutdown of fallback directory mirror armbrust: E781F4EC69671B3F1864AE2753E0890351506329
by Michael Armbruster 26 Jan '19

26 Jan '19

Dear tor-relay list, After a long time maintaining an exit relay that was also chosen to be a fallback directory mirror, I decided that the time has come to shut the relay down. It has only financial reasons (being a cheap server, but still using money out of my own pocket) and I will stay a happy user of Tor and, of course, will provide a new relay as soon as my financial situation gets better. How should we proceed and how long should I still let the fallback mirror run in order to gracefully migrate the fallback status away from my server? I do not want to disappear immediately without any further notice, so I wanted to ask how to further proceed. Kind regards, Michael Armbruster

2 1

Overlay Networks: Research Improvements and Attacks [was: planetlab butterfly relays]
by grarpamp 23 Jan '19

23 Jan '19

On 1/23/19, nusenu <nusenu-lists(a)riseup.net> wrote: > thanks for adding tor relays. > If you are using them for research purposes please ensure > you follow the safety guidelines: > https://research.torproject.org/safetyboard.html > https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… > https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays > | Up | Ext | JoinTime | Nickname | Version | IP | > AS | CC | ORp | Dirp | OS | > Contact | eFamMembers | FP | > https://twitter.com/nusenu_ > https://mastodon.social/@nusenu As many know, many guidelines regarding the stronger distributed encrypted overlay and messaging networks out there are naturally voluntary, and research and attacks are often generally unenforceable and or undetectable when undertaken by qualified adversaries. Many parties [publicly] subscribe to such guidelines, many [silently] don't. That's the nature [and one of the risks] of such networks, indeed of any network. Such adversaries exist and are highly active and capable. Know your adversary. Strengthen your designs to match and best them. As to the nodes, they're all planet-lab.net hosts, planetlab has at least two known tor slices "okstate_tor" and "uml_ZhenLing", some public research outputs [or not] of which might be listed below... https://www.cs.uml.edu/~xinwenfu/paper/TorCellSize_ICC11_Fu.pdf https://www.cs.uml.edu/~xinwenfu/paper/TorWard14_Fu.pdf http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2014_… http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2013_… http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2012_… https://news.okstate.edu/articles/communications/2015/tedx-returns-oklahoma… https://www.youtube.com/watch?v=9QsjkJcUznA MEMEX Christopher White ‎Jiangmin yu, Eric Chan-Tin: Realistic Cover Traffic to Mitigate Website Fingerprinting Attacks DOI: 10.1109/ICDCS.2018.00175 Conference: 2018 IEEE 38th International Conference on Distributed Computing Systems (ICDCS) Identifying Webbrowsers in Encrypted Communications DOI: 10.1145/2665943.2665968 Revisiting Circuit Clogging Attacks on Tor DOI: 10.1109/ARES.2013.17 Conference: Availability, Reliability and Security (ARES), 2013 Eighth International Conference on https://chantin.cs.luc.edu/~chantin/ARES2013.pdf Application Of Data Analytics - Case Studies https://shareok.org/bitstream/handle/11244/54637/Yu_okstate_0664D_15098.pdf

1 0

planetlab butterfly relays
by nusenu 23 Jan '19

23 Jan '19

Hi bf@ctct, thanks for adding tor relays. If you are using them for research purposes please ensure you follow the safety guidelines: https://research.torproject.org/safetyboard.html You care currently not setting the MyFamily option on your relays, which puts tor users at risk. Please configure your relays with MyFamily. more information: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#Whatis… | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+--------------+-----------+-----------------+------------------------------------------+------+-------+--------+-------+---------------+---------------+------------------------------------------| | 1 | 0 | 08:03:03 | butterfly002 | 0.3.5.7 | 200.129.132.19 | Associa\u00E7\u00E3o Rede Nacional de En | br | 9001 | 9030 | Linux | bf(a)ctct.org | 1 | 508BDBDA23A6B76D3C5B2D17DBEA2A4E170859BD | | 1 | 0 | 09:40:10 | butterfly003 | 0.3.5.7 | 216.48.80.12 | University of Ottawa | ca | 9001 | 9030 | Linux | bf(a)ctct.org | 1 | 09F83FDF39A459D91AB8EC18B44A7F389BB5D87C | | 1 | 0 | 09:47:23 | butterfly004 | 0.3.5.7 | 200.17.202.195 | Fundacao da UFPR para o DCTC | br | 9001 | 9030 | Linux | bf4(a)ctct.org | 1 | 7BA8CCC7EFE0D6ED1386173631CC825CB39D6F6F | | 1 | 0 | 11:12:56 | butterfly005 | 0.3.5.7 | 129.97.74.12 | University of Waterloo | ca | 9001 | 9030 | Linux | bf5(a)ctct.org | 1 | ECFFC5A820CBFD37AC2F85AA2C8DC77F87796F16 | | 1 | 0 | 12:07:56 | butterfly006 | 0.3.5.7 | 200.19.159.35 | Associa\u00E7\u00E3o Rede Nacional de En | br | 9001 | 9030 | Linux | bf6(a)ctct.org | 1 | F1F92CC70007DB1EB63B28623B8481863ED3B29F | | 1 | 0 | 12:22:19 | butterfly007 | 0.3.5.7 | 128.8.126.111 | University of Maryland | us | 9001 | 9030 | Linux | bf7(a)ctct.org | 1 | FCA01B39D2CA5DAE896EAAABDB010B0040D068EF | | 0 | 0 | 11:56:55 | butterfly008 | 0.3.5.7 | 192.33.90.67 | SWITCH | ch | 9001 | 9030 | Linux | bf8(a)ctct.org | 1 | 2447A5A12AC3DB748317F97E3317814C42BF0380 | | 1 | 0 | 13:10:27 | butterfly008 | 0.3.5.7 | 133.69.32.131 | Asia Pacific Advanced Network - Japan | jp | 9001 | 9030 | Linux | bf8(a)ctct.org | 1 | 748653AF527B393EFB5870DFA840F8FD578E19BA | | 1 | 0 | 12:36:30 | butterfly009 | 0.3.5.7 | 188.44.50.106 | Federal State Educational Institution of | ru | 9001 | 9030 | Linux | bf9(a)ctct.org | 1 | DCC2DD20CC44DC617A859EA9EFE1A40C5215CAC0 | | 1 | 0 | 13:28:32 | butterfly010 | 0.3.5.7 | 134.117.226.180 | Carleton University | ca | 9001 | 9030 | Linux | bf10(a)ctct.org | 1 | FD82A15B62B73DF4CE20003B651CBB7384C37539 | -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

DNS Server
by dns1983＠riseup.net 23 Jan '19

23 Jan '19

Hello, i'm a student, so I lack many networking notions. Which are the most privacy reliable public dns servers? I don't exactly know how choose a third part DNS server. I read that cloudfare servers are audited by third parties but I'm not sure that I can trust. do you think that audition is trustworthy? Thanks -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.

4 11

Tor meetup @ RADIX hacklab, Athens
by Vasilis 18 Jan '19

18 Jan '19

Dear Tor friends and relay operators, Next Friday (25.01.201) a Tor relay operators meetup will take place at RADIX hacklab, Athens. When: Friday, January 25th, 2019 Time: 19:00 / 7:00 PM Where: Kaniggos 34 & Stournari, Athens 10682, Greece Event link: https://blog.torproject.org/events/tor-meetup-athens Hope to see many of you there. Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Leaky-pipe circuit topology
by marziyeh latifi 18 Jan '19

18 Jan '19

Hello, May you explain me what is Leak-pipe circuit topology? I studied Leaky-pipe circuit topology in "tor- design" document but I don't understand how it work! thanks best regards marzieh

2 1

Bandwidth limiting at relay or network?
by Isaac Grover, Aileron I.T. 17 Jan '19

17 Jan '19

Good evening fellow relay operators, I haven't ever taken the time to configure bandwidth limits in torrc, always preferring to manage it at the firewall as we have other bandwidth limits set there as well. However, I'm curious - what do other relay operators prefer? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - " Because #ProactiveIsBetter " O: 715-377-0440<tel:715-425-0440>, F:715-690-1029<tel:715-690-1029>, W: www.aileronit.com<http://www.aileronit.com/> LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

3 2

Consensus weight drops continuously 28h after getting guard flag
by Ilka Schulz 15 Jan '19

15 Jan '19

Hi, approx. 28 hours after getting the guard flag, my relay <https://metrics.torproject.org/rs.html#details/A99B0D9E5FD5BC3C8F2D006EC91F…>'s consensus weight hit a peak and has declined rather rapidly since then (again 28 hours ago). Did I do something wrong? Is it because I restarted the relay 52 hours ago? Is there actually any detailed documentation on how consensus weight is calculated? Also, my bandwidth (as well as my cpu, etc.) is only used to a fraction of its capacity, even though my relay is three weeks old now. The /RelayBandwidthRate/ option does not limit here... Regards, Ilka

6 11

Torproject onion-repo down (sdscoq7snqtznauu.onion/torproject.org) ?
by petrarca＠protonmail.ch 15 Jan '19

15 Jan '19

Is it just me having issues - today, I couldn't reach the onion-repository of torproject.org at sdscoq7snqtznauu.onion anymore. It was working until very recently though. Everything else is working fine (internet, other onion services, etc.) and I didn't change anything really (just an upgrade to tor 0.3.5.7)...

2 1

Server sale on online.net
by niftybunny 15 Jan '19

15 Jan '19

Tor friendly (even Exist), no bw costs, you should check it out or not. I do not get anything from this. Cheers, markus

1 0

Fallback Directory Mirror
by [REDACTED] 15 Jan '19

15 Jan '19

Hi, i run 17 Entrys and one bridge at the moment. I dont plan to change the IP adresses or the ports and most of them are already paid for nearly two years and i dont see a reason to switch them off after that time so if more fallback directory mirrors are needed then feel free to add them: D379A1CB8285748FFF64AE94296CA89878F25B22 9288B75B5FF8861EFF32A6BE8825CC38A4F9F8C2 EE4AF632058F0734C1426B1AD689F47445CA2056 B57A87009FA838471FB2227DDE68165AB2A2FCC4 465D17C6FC297E3857B5C6F152006A1E212944EA 7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06 39F91959416763AFD34DBEEC05474411B964B2DC 4DC4E6187F1193F2717A5E3DF5ACEBD6B162D5CC 57C6DF5B93E54EB9C8DB90029D9E9A1111BD34D2 3B07C500AC17E7B5A1EE616613E104A094AB87F3 8F6197E5508338B3E3A6BFF59F9EC8F21E1375FB 79E683340B80676DCEB029E48FBD36BC66EBDA1E A86EC24F5B8B964F67AC7C27CE92842025983274 A9DB853547A6459AB5190E62BF2F7B8F068FEB0A Some of them are still pretty new but i am sure they will get older:)

1 0

community team highlights: Relay Advocacy
by nusenu 14 Jan '19

14 Jan '19

FYI -------- Forwarded Message -------- Subject: [tor-project] community team highlights -- November and December Date: Wed, 09 Jan 2019 18:15:00 +0000 From: Alison Macrina <alison(a)torproject.org> Reply-To: tor-project(a)lists.torproject.org To: tor-project(a)lists.torproject.org Relay Advocacy ================================================================== Colin resumed running once a month IRC relay operator meetings. He also started planning the FOSDEM relay operator meet-up. Steph and Colin are working on updating the relay flyers. Colin continues to work on communicating with OVH regarding relays without contactinfo added to the network. Finally, Colin has been working with Bill from EFF on a Tor relay challenge.

9 10

New Fallbacks from December 2018
by teor 14 Jan '19

14 Jan '19

Dear Relay Operators, Thanks to everyone who opted-in their relays as fallback directory mirrors. We rebuilt the list of fallbacks in December 2018. [0] The new list was released in Tor 0.3.5.6-rc, and it was backported to all supported Tor releases. [1] The FallbackDir flags on Consensus Health [2] have been updated. The flags on Relay Search [3] might take a few days to update. Don't worry if your relay missed out this time. It's still helping Tor users. And we will rebuild the fallback list again in 6-12 months time. We are tracking fallback changes in this ticket [4]. To opt-in your relays, add a comment to the ticket [4], or reply to this thread. If you have multiple relays, you can opt-in as many as you like. (We picked up to 7 per operator this time, and we may pick more next time.) T [0]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc https://trac.torproject.org/projects/tor/ticket/24801 [1]: 0.2.9, 0.3.3, 0.3.4, 0.3.5, and 0.4.0. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… [2]: https://consensus-health.torproject.org/graphs.html [3]: For example, this relay is a new fallback: https://metrics.torproject.org/rs.html#details/0C039F35C2E40DCB71CD8A07E97C… [4]: https://trac.torproject.org/projects/tor/ticket/28794 T -- teor ----------------------------------------------------------------------

1 0

Adding Obfuscation Types To Windows Bridge
by Keifer Bly 14 Jan '19

14 Jan '19

Hello, So I am running an obfuscated bridge using the tor expert bundle and the compiled version of obfs4. There are some questions I wanted to ask. So, I am looking to add pluggable transports to my bridge, which currently only supports obfs4. I do not have access to any services that offer domain fronting, or third party servers, so I cannot run meek as a result. However, is it possible to add more than one pluggable transport, such as Format-Transferring Encryption or ScrambleSuit and also have obfs4? Are there compiled versions of these pluggable transports for windows? I also wanted to ask, do I need to update obfs4.exe when I update tor.exe? Another question, so I have in my torrc file, Contact Info: followed by an obfuscated version of this email address. However, as seen on my bridge listing at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032… The contact into does not appear. I do not want to give this email address out publicly, but I do want to register with bridge authorities so they can contact me if something is wrong with my bridge. Here is my torrc, with the ContactInfo line listed. Nickname torland ContactInfo keifer dot bly at gmail dot com SOCKSPort 0 # no local SOCKS proxy ORPort 9002 # public bridge must have an open ORPort ExtORPort auto # configure ExtORPort for obfs4proxy ExitPolicy reject *:* # no exits allowed BridgeRelay 1 # relay won't show up in the public consensus PublishServerDescriptor 1 # publish to the bridge authority # use obfs4proxy to provide obfs4 on port 9003 ServerTransportPlugin obfs4 exec C:\Users\keife\AppData\Roaming\tor\PluggableTransports\obfs4proxy.exe ServerTransportListenAddr obfs4 0.0.0.0:9003 Thanks all very much. --Keifer

1 0

Re: [tor-relays] why the network lost 350 relays and some, bridges
by Argo2 12 Jan '19

12 Jan '19

I was intrigued by the high number of consumer IP's that these relay are supposed to be running on while seemingly automated updating the relay version. The nickname made me look into Ubuntu Snaps as a possible tor distribution which led me to this snap: https://snapcraft.io/tor-middle-relay. It was last updated the 9th of January and when you download the stable snap it is actually named 'snap269'. So the maintainer in this case is the snap maintainer, but not necessarily the relay(s) operator. I have not looked into how these snaps actually work but it may be the case that they actually needed the PortForwaring functionality to get tor running inside a snap. Given that information it could very well be the case that these relays are not running behind a NAT and not run by the same operator but actually by a group of different people. > Date: Sat, 12 Jan 2019 08:07:00 +0000 > From: nusenu <nusenu-lists(a)riseup.net> > >> this occurred when these relays upgraded from tor 0.3.3.10 to 0.3.4.9 >> (package maintainer update) >> >> All these relays were behind NAT devices and they relied on a tor >> feature that got removed between these two versions: >> >>> o Removed features: >>> - The PortForwarding and PortForwardingHelper features have been >>> removed. [...]https://trac.torproject.org/projects/tor/ticket/25409 > > I guess I somehow expected that: the maintainer patched tor 0.3.4.10 to added this > feature again and here we go again with the flood of relays using that version of tor: > > 79 relays from 2019-01-11: > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+-----------------+------------------------------------------+------+-------+--------+-------+-----------+---------------+------------------------------------------| > | 0 | 0 | 01:06:55 | snap269 | 0.3.4.10 | 117.104.229.222 | Instatelecom Limited | af | 43453 | 0 | Linux | None | 1 | CF52FF9F481C618E540D5DACB0C2875F1B7687B5 | > | 0 | 0 | 01:27:25 | snap269 | 0.3.4.10 | 90.253.141.146 | Vodafone Limited | gb | 46089 | 0 | Linux | None | 1 | B483C5FE8A2888F8E02885D8488404DBBEFBCF3B | > [SNIP]

3 3

why the network lost >350 relays and some bridges
by nusenu 12 Jan '19

12 Jan '19

As some of you might have noticed the tor network recently lost a noticeable number of relays and bridges as seen in the metrics.tpo relay graphs (0.7% cw fraction). https://metrics.torproject.org/networksize.html https://pbs.twimg.com/media/DwGAESoXgAEoB6L.jpg this occurred when these relays upgraded from tor 0.3.3.10 to 0.3.4.9 (package maintainer update) All these relays were behind NAT devices and they relied on a tor feature that got removed between these two versions: > o Removed features: > - The PortForwarding and PortForwardingHelper features have been > removed. [...]https://trac.torproject.org/projects/tor/ticket/25409 The portforwarding worked only in about 5% of cases so only 350 of the over 6000 relays actually became reachable. Since I still believe these relays are not run by humans I hope they remain unreachable behind their NAT routers. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

3 4

Tor Relay Configuration: 'MyFamily' missing - byelitehacks
by nusenu 10 Jan '19

10 Jan '19

Hi byEliteHacks, thanks for helping the tor network by running relays. please do not forget to set your "MyFamily" configuration parameter on all your relays, so Tor clients are not at risk of using your relays in multiple positions in a single circuit. https://nusenu.github.io/OrNetStats/endtoend-correlation-groups#conatfynndo… Some more background: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… Let us know if you need any help with this. regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

google Public DNS now Supports DNS-over-TLS
by I 10 Jan '19

10 Jan '19

2 1

torservers.net impersonation: exit relay "Dontbleed9"
by nusenu 07 Jan '19

07 Jan '19

Hi, if you are the operator of the following relay, please stop impersonating torservers.net via ContactInfo and DirFrontPage or risk getting removed from the tor network. +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ | contact | nickname | IP | as_name | efamMembers | +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ | https://www.torservers.net/donate.html <support .AT. torservers .DOT. net> | Dontbleed9 | 213.61.215.54 | COLT Technology Services Group Limited | 1 | +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ https://metrics.torproject.org/rs.html#details/C332CB1924619CF9E74898154232… -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] [OrNetRadar] NickPrefix: "tOr" (14)
by nusenu 07 Jan '19

07 Jan '19

please set a proper contactInfo and MyFamily when running so many relays to avoid getting removed from the network ornetradar(a)riseup.net: > 2019-01-06 > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+-----------------+---------------------+------+-------+--------+-------+-------------------------------------+---------------+------------------------------------------| > | 1 | 0 | 13:47:33 | tOr | 0.3.4.9 | 176.9.73.145 | Hetzner Online GmbH | de | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 27A01740A87B5861DB4008BB81F8CFA518FDA554 | > | 1 | 0 | 15:15:06 | tOr | 0.3.4.9 | 51.15.47.139 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 62E436E252D3657D838AA2D3769530DEB0651BD5 | > | 1 | 0 | 15:18:09 | tOr | 0.3.4.9 | 51.15.179.39 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 430708DD45146CD58C18E34F6EF8E249AF5E2795 | > | 1 | 0 | 15:21:51 | tOr | 0.3.4.9 | 51.15.57.43 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 25E6490C85CCD7B399F816F855BEB1610D8EB56B | > | 0 | 0 | 15:22:12 | tOr | 0.3.4.9 | 51.15.55.204 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 97C183B6ED91CF734F18E3AE08A19D6886F6CA6F | > | 1 | 0 | 15:22:38 | tOr | 0.3.4.9 | 51.15.84.167 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | B9B11438B56875029AD58FC2806D5B6F6546B4F1 | > | 1 | 0 | 15:27:42 | tOr | 0.3.4.9 | 51.15.141.150 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 758022E3952DBA2E74EAA6A7F71FBC7671F50964 | > | 1 | 0 | 15:27:44 | tOr | 0.3.4.9 | 212.47.231.164 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 5935A516784B11A425B6CF82C2740EE53A20C8E7 | > | 1 | 0 | 15:33:08 | tOr | 0.3.4.9 | 51.15.51.3 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 89DDCCBAEBDC2B8C94DA657E8ED6C2FD9A810081 | > | 1 | 0 | 15:35:48 | tOr | 0.2.9.14 | 51.15.92.208 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 0CA7D6634359FC7691AC9159996AD0863D0248FF | > | 1 | 0 | 15:36:54 | tOr | 0.3.4.9 | 51.15.52.4 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | A9A834754E43C80DADCC38E4CF81362F357CABE7 | > | 1 | 0 | 15:37:44 | tOr | 0.3.4.9 | 51.15.84.8 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | B8F0501E3AB911C2EA955EDC30D29B938F5B6B17 | > | 1 | 0 | 15:40:09 | tOr | 0.2.9.14 | 51.15.137.138 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 3FF883A45AEA15721FFFB970EBB7B88719C70E9E | > | 1 | 0 | 15:41:59 | tOr | 0.3.4.9 | 163.172.186.236 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 301F7608C5A6213F381BDBD7010EBB81128E0DAA | > > https://nusenu.github.io/OrNetRadar/2019/01/06/a4 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0