tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Private Tor Research Network
by Nicholas R. Parker (RIT Student) 09 Apr '16

09 Apr '16

Hi all, I've got an issue that I'm seeking help with. I'm with a small group out of RIT that's trying to construct a private TOR network for research purposes, but we've hit a bit of a snag. I've worked with both liu fengyun's ( http://liufengyun.chaos-lab.com/prog/2015/01/09/private-tor-network.html) and Ritter's write up (https://ritter.vg/blog-run_your_own_tor_network.html), but when trying to set up authority directories the whole thing really falls apart. Trying to edit the torrc file gives errors where it doesn't attempt to bind to the correct ports and trying to set --dirserver or --datadirectory results in errors that there isn't permission to access /var/lib/tor regardless of the owner of the directory (we've tried leaving it as being owned by _tor, tried changing ownership to root, etc) so we can't get the authority directories off the ground. I'd really appreciate any thoughts Nicholas R. Parker Rochester Institute of Technology 5thYear, BS/MS Computing Security

2 1

NPR story: When A Dark Web Volunteer Gets Raided By The Police
by Greg 08 Apr '16

08 Apr '16

http://www.npr.org/sections/alltechconsidered/2016/04/04/472992023/when-a-d… A Seattle exit node operator is visited by local police over a child pornography warrant... Is this out of the ordinary or is this to be expected when running an exit from your home IP address?

9 17

Guard flag?
by Clément Février 08 Apr '16

08 Apr '16

Hello, I run a relay for almost 10 days. I wonder if my configuration is correct as I don't see the expected behavior from https://blog.torproject.org/blog/lifecycle-of-a-new-relay Indeed, my consensus weight and the number of connections dropped after 8 days, from 0.0040% to 0.0012% and from 2000 to 300 connections respectively. Since then, I've such messages in arm: [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. [4 duplicates hidden] [NOTICE] We tried for 15 seconds to connect to '[scrubbed]' using exit <fingerprint> at <ip>. Retrying on a new circuit. I was expecting to get a guard flag with an increasing consensus weight involving a drop of the number of connections. So far, I have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid. Is that an evidence something is not running properly? Best, Clèm

9 15

No Daily Digest Anymore
by stealth＠nym.mixmin.net 07 Apr '16

07 Apr '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 About 2 weeks ago I stopped getting a daily digest of this list. Is there a reason for this? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJXBonvAAoJEH1gNwhiMDZu3iIQAJDQ8D+bZ3YG9He4rpQku+Le dHLgodjOckggKnbpfBScqGXQA+mcB9EDIgLQOMtqI3i2SHkjEL9qh5ci0MkZdA7b 0vVJ4Ccbqbn9aupXsbCkrgFA6UT2jz5rys0470FE5gnJiRpBXgAjllBSlZyP00s4 2St+ROqNUTE1chnJlDqTU2iehJWIGDONZUjb+amaUIfsC8MNiokrG0svJZfOsVE5 sRtZ0c+xu3gUnhcM2YaIIV9I+gbFGWTWJPOwZmSIbVoxUmE/Dqg1zHwXeLMSAKJv 5kALfyNZpDtCR62j+pLx1YX2iEHQdr6UaKemwW7HCsXp8ZkbKFwuC7HjP85OoON4 IjqK41KvMxoywD0nvlGbYPw6ssxR9JlMBtg5MqvjlsTPp/aUaUKP/OnjlNGxRwE3 N4fvO8hZPTa8zweykD7qa4RlmJwv0nE+dz/gO3arcz2tIAsC9D90RvD9JGJbeOxW o5yHbIo2h1aHdoelUWMgB5aVdDF30FDAoOZEoSG8DAs8vD6oKFtbWP98f1pVt2Nw dT8J2Q9d4iXe9IEZ8iTNJnyvLIykwqTl+aRJsRD50x7dd3EOzOxF9sKnf/Fq1vto ScNtBVva1fE7LB1kWV8J2LdGGwIwrtR4Af1Hy6rri//E4nvEU2HTnDfVk0dr7ReH uQP+mGr7nPCXLGbXEUp7 =LDGJ -----END PGP SIGNATURE-----

2 1

Getting drops with iptables "-m state --state INVALID" in INPUT and OUTPUT chains on relay
by fr33d0m4all 07 Apr '16

07 Apr '16

Hi… I've noticed that the iptables rule "-m state --state INVALID -j DROP" applied both to INPUT and OUTPUT chains on my raspbian Tor relay drops some connections… is it normal and should I avoid dropping "—state INVALID" connections when the destination or source is the Tor process on the relay? It's strange to have them also in the outgoing chain (i.e. produced by the relay), unless its is related to how Tor works (I'm almost sure that the connections dropped by the OUTPUT rule are related to the Tor process). It's not a matter of conntrack entries, it's using only 61 entries and has a lot of them free. Drop log in the OUTPUT direction => why is my relay sending a packet with ACK PSH FIN flags? iptables-OUT-INVALID-DENIED: IN= OUT=eth0 SRC=10.x.x.x DST=37.x.x.x LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=24372 DF PROTO=TCP SPT=33423 DPT=9001 WINDOW=321 RES=0x00 ACK PSH FIN URGP=0 Drop log in the INPUT direction => This could be a correct drop due to a new connection with RST flag, I think: iptables-IN-INVALID-DENIED: IN=eth0 OUT= SRC=91.x.x.x DST=10.x.x.x LEN=40 TOS=0x00 PREC=0x00 TTL=54 ID=0 DF PROTO=TCP SPT=15754 DPT=9090 WINDOW=0 RES=0x00 RST URGP=0 Best regards, Fr33d0m4All -- _____________________________________________________________ PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4 IRC Nick: fr33d0m4all (OFTC & Freenode) _____________________________________________________________

1 0

Re: [tor-relays] Relays by AS Names
by Tor-Node.net 06 Apr '16

06 Apr '16

ng0 wrote: > Could you upload the .txt of this list to > a network/filepublishing service which > does not require your email > address? I apologize, I was not aware that you had to provide your email to download. Here you can fetch them without providing your email: http://wikisend.com/download/498630/ExoticVPS.ods http://wikisend.com/download/894542/ExoticVPS.xlsx http://wikisend.com/download/789008/ExoticVPS.txt

1 0

Relays by AS Names
by SuperSluether 06 Apr '16

06 Apr '16

I want to host an exit relay, but at the same time I don't want to use a service that already hosts multiple Tor relays. Is there a website that lists relays by AS Names so I can find a service that isn't already populated with Tor?

10 10

Blocking Tor - A case for more accuracy
by Eran Sandler 06 Apr '16

06 Apr '16

https://blog.perimeterx.com/blocking-tor-a-case-for-more-accuracy/ There are certainly other ways of handling Tor traffic and measuring the real intention of a user. Disclaimer: The guys at PerimeterX are friends of mine. I sent them the CloudFlare post (as well as the post from the Tor blog) because I know their methods are much better in detecting intention and not just blocking Tor IPs. Eran

1 0

Relay request
by runner7272 04 Apr '16

04 Apr '16

Sent from my Sprint Phone.

2 1

Re: [tor-relays] tor-relays Digest, Vol 63, Issue 5
by d3part3d＠tuta.io 04 Apr '16

04 Apr '16

? -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 4. Apr 2016 15:31 by tor-relays-request(a)lists.torproject.org: > Send tor-relays mailing list submissions to > > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Tor Weather has been discontinued (Karsten Loesing) > 2. Re: Tor Weather has been discontinued (Eran Sandler) > 3. Re: Tor Weather has been discontinued (Eran Sandler) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Apr 2016 16:48:39 +0200 > From: Karsten Loesing <> karsten(a)torproject.org> > > To: > tor-relays(a)lists.torproject.org > Subject: [tor-relays] Tor Weather has been discontinued > Message-ID: <> 57027EC7.9010802(a)torproject.org> > > Content-Type: text/plain; charset=utf-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dear relay operators, > > as of April 4, 2016, Tor Weather has been discontinued. > > Tor Weather [0] provided an email notification service to any user who > wanted to monitor the status of a Tor node. Upon subscribing, they > could specify what types of alerts they would like to receive. The > main purpose of Tor Weather was to notify node operators via email if > their node was down for longer than a specified period, but other > notification types were available, including one where operators would > be informed when their node was around long enough to qualify for a > t-shirt. > > The main reason for discontinuing Tor Weather is the fact that > software requires maintenance, and Tor Weather is no exception. Tor > Weather was promising t-shirts for relays that have not been around > long enough or that provided too little bandwidth to be useful to the > network, and it was almost impossible to deny a t-shirt after Tor > Weather has promised it. Apart from that, Tor Weather was likely not > offering t-shirts to people who have long earned it, thereby confusing > them. An unreliable notification system is worse than not having a > system at all. Relay operators shouldn't rely on Tor Weather to > notify them when their relay fails. They should rather set up their > own system instead. > > We have tried to find a new maintainer for Tor Weather for years, but > without success. We started rewriting Tor Weather [1] using Onionoo > [2] as data back-end in 2014, and even though that project didn't > produce working code, somebody could pick up this efforts and finish > the rewrite. The Roster developers said that they're planning to > include an email notification function in Roster [3]. And we > developed a simple Python script that provides information about a > relay operator's eligibility for acquiring a t-shirt [4]. None of > these alternatives is a full replacement of Weather, though. > > We encourage you, the community of Tor relay operators, to step up to > start your own notification systems and to share designs and code. > Tor Weather is still a good idea, it just needs somebody to implement it. > > Tor Weather is discontinued in two steps. For now, new subscriptions > are disabled, new welcome messages are not sent out anymore, and > existing subscriptions continue working until June 30, 2016. From > July 1, 2016 on, Tor Weather will not be sending out any emails. > > Sorry for any inconvenience caused by this. > > All the best, > Karsten > > > [0] > https://weather.torproject.org > > [1] > https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 > > [2] > https://onionoo.torproject.org > > [3] > http://www.tor-roster.org > > [4] > https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py > > -----BEGIN PGP SIGNATURE----- > Comment: GPGTools - > http://gpgtools.org > > iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 > WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF > xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE > ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i > gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER > VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= > =LVj8 > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 2 > Date: Mon, 04 Apr 2016 14:58:20 +0000 > From: Eran Sandler <> eran(a)sandler.co.il> > > To: > tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Tor Weather has been discontinued > Message-ID: > <> CALR3k-G0DoeRB-baVw+uvGUeMdDRVMORwEgAjDgCg6kE3n1cGQ(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > I have played quite a bit with onionoo and wrote a wrapper in Go for it. > > I am willing to rewrite Tor Weather using Go (or python if you like). > > I'll go over the old code and this email again to make sure I understand > the full scope of the project. > > As an operator I have relied on the Tor Weather alerts to know if one if my > nodes were down and while it's wasn't quick enough in sending alerts it was > a good tool. > > I have some ideas about the t-shirts alerts so that we won't miss sending > to those that need it and wouldnt send to those that don't need it. > > Eran > > On Mon, Apr 4, 2016, 17:49 Karsten Loesing <> karsten(a)torproject.org> > > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Dear relay operators, >> >> as of April 4, 2016, Tor Weather has been discontinued. >> >> Tor Weather [0] provided an email notification service to any user who >> wanted to monitor the status of a Tor node. Upon subscribing, they >> could specify what types of alerts they would like to receive. The >> main purpose of Tor Weather was to notify node operators via email if >> their node was down for longer than a specified period, but other >> notification types were available, including one where operators would >> be informed when their node was around long enough to qualify for a >> t-shirt. >> >> The main reason for discontinuing Tor Weather is the fact that >> software requires maintenance, and Tor Weather is no exception. Tor >> Weather was promising t-shirts for relays that have not been around >> long enough or that provided too little bandwidth to be useful to the >> network, and it was almost impossible to deny a t-shirt after Tor >> Weather has promised it. Apart from that, Tor Weather was likely not >> offering t-shirts to people who have long earned it, thereby confusing >> them. An unreliable notification system is worse than not having a >> system at all. Relay operators shouldn't rely on Tor Weather to >> notify them when their relay fails. They should rather set up their >> own system instead. >> >> We have tried to find a new maintainer for Tor Weather for years, but >> without success. We started rewriting Tor Weather [1] using Onionoo >> [2] as data back-end in 2014, and even though that project didn't >> produce working code, somebody could pick up this efforts and finish >> the rewrite. The Roster developers said that they're planning to >> include an email notification function in Roster [3]. And we >> developed a simple Python script that provides information about a >> relay operator's eligibility for acquiring a t-shirt [4]. None of >> these alternatives is a full replacement of Weather, though. >> >> We encourage you, the community of Tor relay operators, to step up to >> start your own notification systems and to share designs and code. >> Tor Weather is still a good idea, it just needs somebody to implement it. >> >> Tor Weather is discontinued in two steps. For now, new subscriptions >> are disabled, new welcome messages are not sent out anymore, and >> existing subscriptions continue working until June 30, 2016. From >> July 1, 2016 on, Tor Weather will not be sending out any emails. >> >> Sorry for any inconvenience caused by this. >> >> All the best, >> Karsten >> >> >> [0] >> https://weather.torproject.org >> >> [1] >> https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 >> >> [2] >> https://onionoo.torproject.org >> >> [3] >> http://www.tor-roster.org >> >> [4] >> https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py >> >> -----BEGIN PGP SIGNATURE----- >> Comment: GPGTools - >> http://gpgtools.org >> >> iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 >> WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF >> xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE >> ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i >> gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER >> VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= >> =LVj8 >> -----END PGP SIGNATURE----- >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays