- tor-relays - lists.torproject.org

Go home GeoIP, you're drunk.
by Ralph Seichter 07 Aug '17

07 Aug '17

I moved a Tor relay to new hardware, keeping the keys. Both old and new server are located in Germany and provided by the same hosting company. After the latest Atlas update, I was surprised to see that the IPv4 address is listed as belonging to an AS in Ukraine. A little more digging returned Guangzhou, China, as the supposed location based on the server's IPv6 address. Is there anything I can/should do about this (I doubt it)? Will this affect my Tor node consensus weight? As it is not an exit node, I am hoping it won't matter much. -Ralph

7 9

HOW-TO: Simple DNS resolver for tor exit operators
by Dennis Emory Hannon 07 Aug '17

07 Aug '17

Hello friends, I decided to make a quick starter guide to introduce using a local resolver for tor-exit node operators. I'd like to solicit some of your feedback on things that should be added or improved upon. Hopefully this will be a living document - My goal is to help lower the amount of TOR exit relays using 3rd party DNS providers for client DNS lookups. While it doesn't address all security concerns, it's a necessary step to improving anonymity of TOR's users. Let me know what you think. Guide is meant for debian/linux users http://backplanedns.org/TOR_exit_dns_resolver_howto.htm -Dennis

6 6

Tor relay operators at SHA2017 ?
by Schroedinger 07 Aug '17

07 Aug '17

Hi relay operators, if anyone at SHA2017 is interested in meeting up, perhaps we could set up a self-organized session for Tor relay operators.

4 5

Re: [tor-relays] Tor relay operators at SHA2017 ?
by Alexander Dietrich 07 Aug '17

07 Aug '17

There is a self-organized session now: https://wiki.sha2017.org/w/Session:Tor_Relay_Operators_Meetup Cheers, Alexander Sent from my toasterOn Aug 5, 2017 5:46 PM, Alexander Færøy <ahf(a)0x90.dk> wrote: > > On 1 August 2017 at 21:24, Schroedinger <schroedingers_cat(a)riseup.net> wrote: > > if anyone at SHA2017 is interested in meeting up, perhaps we could set > > up a self-organized session for Tor relay operators. > > I'm here as well. I'll happily meet and talk about Tor! > > Cheers, > Alex. > > -- > Alexander Færøy > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Fwd: Your TOR relay
by Tom van der Woerdt 07 Aug '17

07 Aug '17

:-( If you got this mail as well, please don't fall for it. You'd be exposing Tor users' browsing data. Tom -------- Doorgestuurd bericht -------- Onderwerp: Your TOR relay Datum: Sun, 6 Aug 2017 21:19:32 -0400 Van: Dennis Hannon <dennis.hannon(a)backplanellc.com> Aan: Dennis Hannon <dennis.hannon(a)backplanellc.com> Hello, I came across your TOR relay on atlas. I run a few relays myself along with a bunch of DNS resolvers which are a part of the Open Root Server network (ORSN.org) - aimed to fight internet censorship and circumvent government surveillance programs (ie. prism). I hope you may be interested in using our anonymous open DNS resolvers on your node. http://BackplaneDNS.org Resolver - 172.98.193.42 Resolver - 162.248.241.94 ------------------------------------------------------ Hostmaster@: Mr. Dennis Emory Hannon Phone: +1 (585) 735-5996 E-Mail: info(a)backplanedns.org abuse(a)backplanedns.org

1 0

prop224 warning
by Logforme 03 Aug '17

03 Aug '17

Saw a new thing in my tor log today: Aug 01 11:07:27.000 [warn] Established prop224 intro point on circuit 799774346 According to google, prop224 is a new hidden service protocol? https://trac.torproject.org/projects/tor/ticket/12424 Which sounds like a great thing. But why do I get a warning about it? My relay: https://atlas.torproject.org/#details/855BC2DABE24C861CD887DB9B2E950424B49F…

2 2

freebsd-ports; tor, obfs4, browser & socks
by Vinícius Zavam 02 Aug '17

02 Aug '17

hello everyone, I'm writing to inform that our efforts to keep sharp with Tor support on FreeBSD are still alive. although we (TDP, https://torbsd.github.io) would like to call more people to help testing these ports we changed and created. the signed source code is available at https://github.com/torbsd/freebsd-ports/releases/tag/tdp sorry for the superficial bump, cross-posting and not much detailed email. kr, -- Vinícius Zavam keybase.io/egypcio/key.asc

1 0

MyFamily consensus byte savings
by grarpamp 02 Aug '17

02 Aug '17

Consensus could save ~500kB (3%) by clients automatically swapping MyFamily from config plaintext format to bitmap selection from DA provided list of recently seen node FP's before publishing descriptor.

2 1

Want to help test 'Sandbox 1'? (Linux only)
by nusenu 02 Aug '17

02 Aug '17

Hi, I'm aiming to enable tor's 'Sandbox' feature by default on Debian based relays starting with the next release of ansible-relayor [1]. Before doing so I'd like to collect some feedback from tor relay operators willing to test this feature. If you - run tor 0.3.0.x >= 0.3.0.8 - are on Linux - willing to report proplems it would be greate if you could add the following line to your torrc configuration file: Sandbox 1 Ideally you have also a system monitoring in place that tells you whether this config change has any impact (i.e. on CPU or bandwidth). [1] https://github.com/nusenu/ansible-relayor -- https://mastodon.social/@nusenu https://twitter.com/nusenu_

5 6

Util helping maintain MyFamily
by Ryru 02 Aug '17

02 Aug '17

Hello Everyone I wrote a bash script helping maintaining the MyFamily string in torrc. The idea is to have one single file with all relay nicknames and there fingerprints and generate the MyFamily string uniquely for every node in the family. You will find a copy here: https://github.com/ryru/myfam If you like a bit more background check out: https://blog.addere.ch/2017/07/13/myfam-a-utility-helping-you-maintaining-y… Hope this helps anyone! cheers pascal

2 1