- tor-relays - lists.torproject.org

Relay "kingqueen" lost Named attribute
by kingqueen 22 Aug '14

22 Aug '14

hi, Does anybody know why my relay "kingqueen" has lost its Named attribute? https://atlas.torproject.org/#details/7B48192A59A903F914ECF73ADBC3711F3E8EA… Thank you KQ

3 3

Re: [tor-relays] OnionTip.com distributes Bitcoin donations to all BTC addresses set in ContactInfo
by Tim 21 Aug '14

21 Aug '14

On 14 Aug 2014, at 22:00, Alexander wrote: >> On 2014-08-14 10:25, Mike Cardwell wrote: >> >> On the other hand. It costs you nothing to stick a bitcoin >> address in a config file to find out. > > Not being a lawyer, does accepting money for running a Tor relay make it > a commercial operation (in some countries) and put you in a different > legal position? > > Best regards, > Alexander Also not being a lawyer, if BTC isn't legal tender in your country (if such a concept exists), are you really accepting "money"? Tim

3 3

reaching out to relay ops that run outdated versions
by Nusenu 19 Aug '14

19 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 FYI: I just sent out the email bellow to ~160 relay operators - I hope this results in some actual improvements. It is a bit disappointing to see even torservers.net, DFRI, icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list. The recipient list is based on the following output (limited to relays faster than 999KB/s): grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de) > Hello, > > you are receiving this email because you are using an outdated tor > version on your tor relay. (your email address was taken from your > relay's contact info field) > > Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a > security issue that makes de-anonymization attacks easier [2] - > please update to Tor v0.2.4.23 or v0.2.5.6. > > To find out your current version run the following command on your > relay: tor --version > > If you are using Linux: Package managers can be used to > automatically update Tor without requiring manual admin > intervention. > > > It is recommended to use the official APT/YUM repos from > torproject.org to get timely updates: APT: > https://www.torproject.org/docs/debian.html.en YUM: > https://www.torproject.org/docs/rpms.html.en > > > thanks for running a relay and making the tor network safer! > > > [1] > https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html > > [2] > https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html > -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT8IfkAAoJEDcK3SCCSvoecIMP/0NX+C4+h55BXaQt2RSwA472 PyEIjSRUwrlnc0navJ1pSHOusCWnrCiMFXQaQqcdCliODzEytPoaLynItiwAtKzp UhDja4Sp/Lag9m9CiNJ/0C9k9OeHQbKcEffLAnTVUOZmcBFwo2CsROruGgveOic6 gE13Yi9LuoHdtMfDDRgLoQyL5hqa1kogpj9maMjXZwEwXhZvNpd7GEUd79WjtVm+ eFoYTW4mgPXcU0fZOtuZxAAkrd/blEzr67o4aKiMeaNDo6zmXIBe1URsPkRf50dO kQ0m4/GSicdVyOnsId+f6RcpAD/LD7QiqIyxv/XZ9uEDqtI2RvxBxNeU9kXU8KK+ y4fsXKZ4pvXgj5Nqv7niNJlftegr1rrdRB7wAtZ/2ETpEL3dqC+aBo0bL+ctk1zZ RlXZkPTOTmGEh5pDxXr8P1rxukgivOsPw3tWmeCjb2+HeiRi117LNeccvwW3SZYE pDLVSJIhxpkFKxtJ8N4vTyqoQzX/N+g1gkOZ/yuF4aCIpfLFTxjUUkMt8wyEI+v2 HMiAXyeHBFh541b9ScTrLao21sxPDsQHq1mNf3RHRKESgiejWLZz74wojUU/drIP coZVoJ7U3aFqb6xgIlJzv8u+IcPld6Xsy3U8MUtD+4q2v7t9y6u6QBrj454YCQrQ Ms0g2ocOvRCTKWUgtbdx =BK/o -----END PGP SIGNATURE-----

9 17

Protecting your domain's reputation
by JusticeRage 19 Aug '14

19 Aug '14

Hello everyone! I am the operator of a somewhat recent exit node with SMTP allowed, and I have found out something worth sharing. Let me know if this is already known. As suggested by the Tor documentation, I set a reverse DNS which makes clear that my exit node belongs to the Tor network (tor-exit-readme.manalyzer.org) This week-end, I started to recieve weird e-mail delivery failure notifications, and even a line from a guy kindly asking me to stop sending him mail. The thing is, I was actually lucky to recieve all those, and I wouldn't have if I didn't have a catch-all address set for the whole domain. Looking at the source of the rejected e-mails, I found out that someone was forging e-mails which look like they come from my domain: Received: from tor-exit-readme.manalyzer.org (tor-exit-readme.manalyzer.org [95.130.11.147]) by smtp.craigslist.org (Haraka/2.5.0) with ESMTP id 66DDCADC-FEA4-4D62-8F08-2630AC1E0299.1 envelope-from <best_pharmacy5(a)manalyzer.org>; Mon, 18 Aug 2014 13:25:12 -0700 From: Levitra-Shop <best_pharmacy5(a)manalyzer.org> To: <rkdq8-4339052657(a)hous.craigslist.org> Subject: When It Comes Healthcare, Nothing Beats a Hometown Advantage, Rkdq8-4339052657 . (I got tons of these, all procedurally generated e-mail addresses.) The thing is, these e-mails don't just seem like they're coming from my domain: they ARE coming from my domain, since the machine sending them has a rDNS which belongs to it. From a mail server's perspective, they're actually very legitimate and probably won't be flagged as spam. I believe that someone is listing all the exit nodes which have a reverse DNS set up, and uses the domain to send out unwanted e-mail. This is a problem for operators for the following reasons: - The reputation of your domain is damaged, and legitimate e-mails sent from it may end up discarded - It strenghtens the idea that mail servers blindly reject everything that comes out of a Tor exit node The good news is, there is something you can do about it. This is exactly what Sender Policy Framework [1] was created for. Long story short, this is some information you can put in your DNS to indicate which machines are allowed to send e-mails for the domains, and which are not (hint: the exit node should not be listed in there). Here is a sample policy which says that only servers registered as MX in your DNS should send e-mails for the domain : tor-exit.domain.com. IN TXT "v=spf1 mx -all" If you need something more specific, I have found a nice wizard [2] which will help greatly. If you run an exit node and have a reverse DNS set up, I highly recommend you take ten minutes to look into this. Please note that this will NOT prevent Tor users from sending e-mail or restrain their freedom in any way; it will only prevent ill-intentioned people from spoofing your domain. I also think that there should be a note in the Tor documentation about this issue (I couldn't find anything regarding this). I hope this helps! [1] https://en.wikipedia.org/wiki/Sender_Policy_Framework [2] http://www.spfwizard.net/ -- JusticeRage

3 3

Web status page
by IceFish ThreeTwo 19 Aug '14

19 Aug '14

Is there a -- Sent from my iPhone

2 2

Include Tor Weather Link
by Spencer Rhodes 18 Aug '14

18 Aug '14

If another email goes out to operators of outdated Tor relays, I would suggest including some information and a link to the Tor Weather service, which has an option to notify via email if the software version is outdated. -- Sent from my phone.

2 1

Dynamic IP
by Tim 18 Aug '14

18 Aug '14

Tim Wilson-Brown E: twilsonb(a)mac.com > Date: Mon, 18 Aug 2014 05:04:31 +0200 > From: Sebastian Hahn <mail(a)sebastianhahn.net> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Dynamic IP > Message-ID: <CD0E96E4-2BFA-4FAA-BC19-C3320AC46F08(a)sebastianhahn.net> > Content-Type: text/plain; charset=us-ascii > > Hi Tim, > >> Sebastien, I run a relay on a machine that has an internal private IP, behind a NAT router with a public IP. >> >> In my experience, I need to specify the NAT router's public IP in the torrc, otherwise tor doesn't include it in the router descriptor it submits to the consensus. > > This shouldn't happen typically, Tor tries to learn its IP address by > looking at the traffic it receives. > >> If that process isn't working for me, is this a bug I should report? > > Likely. Can you try again, noting the kind of log messages Tor might > emit? > I apologise, Sebastien, it appears I was not waiting long enough for the router to connect to a directory, then use the headers to find its IP. I had always assumed that the first series of failures to find an IP (before any directories were contacted) was permanent. This is the debug log output from a secondary test router that I configured on the same IP: Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Guessed local hostname 'REDACTED.local' resolves to a private IP address (192.168.REDACTED.REDACTED). Trying something else. Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Interface IP address '192.168.REDACTED.REDACTED' is a private address too. Ignoring. Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Address 'REDACTED.local' resolves to private IP address '192.168.REDACTED.REDACTED'. Tor servers that use the default DirAuthorities must have public IP addresses. Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const or_options_t *, uint32_t *)(): Could not determine our address locally. Checking if directory headers provide any hints. Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const or_options_t *, uint32_t *)(): Success: chose address '121.REDACTED.REDACTED.REDACTED'. Once the test router appears in the consensus, I'll make similar changes to the primary router (and it will pick them up on the next restart!) Tim

1 0

Close friend
by IceFish ThreeTwo 18 Aug '14

18 Aug '14

Hello. I'm not going to use the term "Framily", Sprint can...nsfw. Anyways, my close friend just set up a Tor node. I'm pretty sure I read somewhere that the Family option in torrc is used so that nodes administrated by the same person never make a circuit with each other, which somehow protects anonymity. Should my friend and I put each other's fingerprints in the Family field? Seems logical since we know each other and if the point of theFamily field is to protect anonymity. Thanks! Ice Fish -- Sent from my iPhone

4 4

Dynamic IP
by Tim 18 Aug '14

18 Aug '14

> On Sun, 17 Aug 2014 00:42:13 +0200, Sebastian Hahn <mail(a)sebastianhahn.net> wrote: > > Date: Sun, 17 Aug 2014 00:42:13 +0200 > From: Sebastian Hahn <mail(a)sebastianhahn.net> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Dynamic IP > Message-ID: <90ABDCE9-CC09-4892-9935-F7B7C78832E9(a)sebastianhahn.net> > Content-Type: text/plain; charset=us-ascii > > Hi Tim, > >> On 16 Aug 2014, at 23:53, Tim <t_ebay(a)icloud.com> wrote: >> I'm running a relay on a similarly "dynamic" IP. >> If the line goes down, I'm reallocated a new one. But otherwise the IP is stable. >> If I don't notice the change, I notice the traffic drop, then I update the torrc, and everything works again. > > I think you're a little confused. It's not necessary to specify your own > IP address in Tor's configuration file. The various "address" options are > purely optional. Or I am confused, and you mean something completely > different? > Sebastien, I run a relay on a machine that has an internal private IP, behind a NAT router with a public IP. In my experience, I need to specify the NAT router's public IP in the torrc, otherwise tor doesn't include it in the router descriptor it submits to the consensus. How does tor autodetect its public IP, when it is running on a separate machine with a private network IP, behind a NAT router with a public IP? If that process isn't working for me, is this a bug I should report? If tor doesn't currently autodetect public IPs on middleboxes (as opposed to the tor relay machine itself), is this a feature that could be implemented? Or do we wish to discourage this use case? (It would involve trusting an external server to report tor's public IP correctly - and making other assumptions like the middlebox having a single public IP.) Tim

2 1

Number of relays by version
by Jesse Victors 17 Aug '14

17 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey guys, Today on Reddit I saw a post on /r/Tor that listed the number of relays by version, which was pretty cool. While OP apparently loaded the information into SQLite and selected the count, there's another way to do it: sudo cat /var/lib/tor/cached-microdesc-consensus | grep '^v ' | awk '{print $3}' | sort | uniq -c Which currently gives: 2 0.2.3.20-rc 5 0.2.3.22-rc 3 0.2.3.24-rc 579 0.2.3.25 1 0.2.4.10-alpha 2 0.2.4.11-alpha 5 0.2.4.15-rc 15 0.2.4.16-rc 23 0.2.4.17-rc 4 0.2.4.18-rc 12 0.2.4.19 271 0.2.4.20 351 0.2.4.21 998 0.2.4.22 3 0.2.4.22-dev 3209 0.2.4.23 7 0.2.4.23-dev 3 0.2.5.1-alpha-dev 9 0.2.5.2-alpha 22 0.2.5.3-alpha 5 0.2.5.3-alpha-dev 28 0.2.5.4-alpha 4 0.2.5.4-alpha-dev 47 0.2.5.5-alpha 232 0.2.5.6-alpha 29 0.2.6.0-alpha-dev I find the distribution interesting. 0.2.3 is dwindling, but for those 589 that remain, please be aware 0.2.4 is available, so be sure to update or change to the official Tor repos. Looks like 0.2.6.0 is the tip of the spear now. - -- Jesse V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCQBmBQJT8FBhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yAFCMIAMBzJko9CDSqfEyiPFZzNVy8 ZNlr4ZBekm9aLG2cJEVD2zN2wLc0mWb/ETFrbVNbauWIEvuNjchE0xZRXMUJBrFT L9ErUmNeGWEr77XXYAawoOI4PDPXOF4SIMQUdAel8OVCZ5g0UYARDlfIBgwVeq+o LnvSrDdv/hcwIxsrLxX+J/XqwXOIDnxhjMu6MnHG7YDXGameACbMl4OfOCgXVNT9 VV9YLATJq1nHr5F5I8xmDU5RVUsVRccn8POBHgTfZwDtwMy3N6U/wQqFY0XzslLH wY2veoPcuIoL8x1Sz81vK9Buc9oD/F06HzrZRW2WHg2Tw8yJYFizVyWpOlQ/xKs= =NIsd -----END PGP SIGNATURE-----

2 1

Re: [tor-relays] Dynamic IP
by Tim 16 Aug '14

16 Aug '14

I'm running a relay on a similarly "dynamic" IP. If the line goes down, I'm reallocated a new one. But otherwise the IP is stable. If I don't notice the change, I notice the traffic drop, then I update the torrc, and everything works again. Wouldn't it be great if there was an option for tor to do this automatically? But this would involve trusting google or similar to correctly report the external IP (and not get MITMed). I tried running a bridge, but it made almost no use of the available bandwidth. But if the IP were more dynamic, a bridge would be an excellent choice, as long as I could keep the config synced with the external IP. This would be the core use case for a tor "use dynamic external IP" option. (And the current "guess my IP" option doesn't work for me, as it's the internet-visible external IP I need, not the relay's internal network IP.) > On 17 Aug 2014, at 6:45, IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> wrote: > > Date: Sat, 16 Aug 2014 13:09:08 -0700 > From: IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> > To: "tor-relays(a)lists.torproject.org" > <tor-relays(a)lists.torproject.org> > Subject: Re: [tor-relays] Dynamic IP > > Alright thanks. Yeah it's a "dynamic" IP. I bet they just say that in case > they have to change it for some reason. > >> On Saturday, August 16, 2014, justaguy <justaguy(a)riseup.net> wrote: >> >> That's not a big deal, if it's once every 8 months. >> But every day, that would be a problem. >> If you keep running your relay for 8 months, and then an ip change, i >> think it will be back at normal speeds in like 5 minutes >> On 08/16/2014 10:04 PM, IceFish ThreeTwo wrote: >> >> Unfortunately my ISP only provides static IPs for their business accounts, >> which, even if in my price range, I can't get at my home because of zoning. >> My IP hasn't changed once since I got the service and I think I've kinda >> locked it in with my router. But if it does switch say once every 8 months, >> how big of a deal is that? >> >> On Saturday, August 16, 2014, justaguy <justaguy(a)riseup.net >> <javascript:_e(%7B%7D,'cvml','justaguy(a)riseup.net');>> wrote: >> >>> Yes, other relays don't like your relay changing ip's all the time. >>> You should try to get a static ip somehow, ask your isp :) >>> On 08/16/2014 10:00 PM, IceFish ThreeTwo wrote: >>> >>> I have a dynamic IP from my ISP. Is that going to cause issues with my >>> relay? >>> >>> -- >>> Sent from my iPhone >>> >>> >>> _______________________________________________ >>> tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> -- >> Sent from my iPhone >> >> >> _______________________________________________ >> tor-relays mailing listtor-relays(a)lists.torproject.org <javascript:_e(%7B%7D,'cvml','tor-relays(a)lists.torproject.org');>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > -- > Sent from my iPhone >

2 1

Getting things right
by Graeme Briggs-White 16 Aug '14

16 Aug '14

I have a rooted Samsung S3 with CM 11 4.4.4 nightly build and would like to know exactly how to get the best for everyone involved on the network. My problem seems to be ram capacity and have tried every which way to improve that. Nothing seems to work as it has under 1 Gig of ram. How do I configure this for the best and not piss other users off. My binary skills are none too great but I'm willing to learn and am open to harsh comments to get me on my way. I'm quite a newbee at this and open to criticism.....

3 13

Dynamic IP
by IceFish ThreeTwo 16 Aug '14

16 Aug '14

I have a dynamic IP from my ISP. Is that going to cause issues with my relay? -- Sent from my iPhone

3 5

Re: [tor-relays] tor-relays Digest, Vol 43, Issue 15
by Spencer Rhodes 16 Aug '14

16 Aug '14

Hi Matt, Thanks for the quick reply. The servers did not show because I had commented out the Nickname line in /etc/tor/torrc after seeing a notice in arm that it was redundant (presumably because it is identical to the hostname). Apparently, not redundant after all as it is necessary for proper listing on the torstatus servers… So, I browsed to your suggested URL and verified that for my server which does show the Directory flags, it returns a bunch of data: http://99.28.48.185/tor/status-vote/current/consensus, but for the server which is now lacking the flags, nothing is returned: http://80.240.141.246/tor/status-vote/current/consensus. As far as I know, these servers are identically configured apart from the nicknames, fingerprints, and bandwidth. And as I said, initially both servers showed Directory flags. I am running on Debian, and so tried "service for restart” without effect. Hate to have to reinstall to get Directory services up again… Best regards, Spencer On Aug 13, 2014, at 1:28 PM, tor-relays-request(a)lists.torproject.org wrote: > > > From: Matthew Finkel <matthew.finkel(a)gmail.com> > Subject: Re: [tor-relays] Directory Server Issue > Date: August 13, 2014 at 12:08:58 PM EDT > To: tor-relays(a)lists.torproject.org > Reply-To: tor-relays(a)lists.torproject.org > > > On Wed, Aug 13, 2014 at 10:32:45AM -0400, Spencer Rhodes wrote: >> Hi, >> >> I have a server (triratna) which I recently put up, which operates on ports 80 and 443, and which initially showed a Directory Server flag. After several days of operation, however, the directory flag disappeared from both the torstatus listing and from the arm display on the console. >> >> I would like to know if there is a way to verify that directory services are in fact working, and if so, determine why the server is not flagged properly. I found some old postings to the effect that one could browse to server://tor or server://tor/status/all, but this does not seem to be true any more. > > Hi Spencer, > > This should still work. Try using > http://<ip address>:<DirPort>/tor/status-vote/current/consensus > to fetch the current consensus. You can also fetch individual relay > descriptors using a similar URI. > > If you provide your relay fingerprint someone may be able to help > further. I tried looking up the name you gave, but I couldn't find > it in either Globe[0] nor Atlas[1]. > > Thanks for running a relay! > > - Matt > > > [0] https://globe.torproject.org/#/search/query=triratna > [1] https://atlas.torproject.org/#search/triratna > >

1 1

Re: [tor-relays] Advertised Bandwidth
by Mike Patton 16 Aug '14

16 Aug '14

Hey there, The advertised bandwidth will increase gradually. Well mine did. M. On 16/08/2014 10:28 am, IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> wrote: > > Hello! > > I'm unclear as to what the "Advertised Bandwidth" is on Atlas. My node has it's bandwidth set to 700Kb/s, however on Atlas the Advertised Bandwidth is around 7Kb/s. I'm on day three of running this relay and I have read the Early Lifecycle blog post, but I'm still confused as to why the Advertised Bandwidth is a hundredth of what I have it set to. > > Thank you! > Ice Fish > > > -- > Sent from my iPhone

3 2

Advertised Bandwidth
by IceFish ThreeTwo 16 Aug '14

16 Aug '14

Hello! I'm unclear as to what the "Advertised Bandwidth" is on Atlas. My node has it's bandwidth set to 700Kb/s, however on Atlas the Advertised Bandwidth is around 7Kb/s. I'm on day three of running this relay and I have read the Early Lifecycle blog post, but I'm still confused as to why the Advertised Bandwidth is a hundredth of what I have it set to. Thank you! Ice Fish -- Sent from my iPhone

1 0

Exit node dropped to near zero weight
by Bill Winslow 15 Aug '14

15 Aug '14

Hi everyone, https://globe.torproject.org/#/relay/5B06042B4911171026059FB694215B97D10E47… I've been running an exit node for a few days now, and around 8 hours ago my consensus weight and exit probability dropped to essentially zero, after dropping substantially several hours previously. Why is that? Nothing in my logs suggests anything unusual -- but then again, I'm very new to this and thus wouldn't know where else to look or what to think about this. http://pastebin.com/mfkbPK9L Thanks for your time.

2 2

Re: [tor-relays] OnionTip.com distributes Bitcoin donations to all BTC addresses set in ContactInfo
by Mike Patton 14 Aug '14

14 Aug '14

On 14 Aug 2014 08:34, Ed Carter <ecarter9(a)riseup.net> wrote: > > > Tim Semeijn schreef op 10/08/14 17:33: > >> On 8/10/14, 4:32 PM, ban(a)unseen.is wrote: > >>> Hi, > >>> > >>> apparently this hasn't been discussed here yet. About a month ago, > >>> Donncha O'Cearbhaill build https://oniontip.com/ during the Dublin > >>> Bitcoin Hackathon. It is a webapp which automatically extracts all > >>> Bitcoin addresses set in the ContactInfo variable of the torrc and > >>> distributes Bitcoin donations based on the consensus weight. > >>> > >>> There are already 100+ relays listed which represent around 5% of > >>> the total consensus weight. In just a few weeks they distributed > >>> around 125 US$. > >>> > >>> There are many other theoretical ways to provide compensation to > >>> tor relay operators (see > >>> https://blog.torproject.org/blog/tor-incentives-research-roundup-goldstar-p…) > >>> > >>> > >> but I really like this very simple and practical approach. > >>> > >>> Thoughts? _______________________________________________ > >>> tor-relays mailing list tor-relays(a)lists.torproject.org > >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >>> > >> > >> I myself added a bitcoin address to the ContactInfo variable of my > >> nodes when I saw a tweet about this initiative. It is a nice way to > >> offer a way to donate to multiple node running volunteers instead of > >> donating to a specific person or organization. > >> > >> My nodes take up 20% of the current donations based on consensus so it > >> would be nice if more relay operators take part in this project to > >> make it resemble the current Tor network better. > > > > I really like this and I've added an address to my exits (4.2% of total > > exit consensus). However, for this to really kick off I'd recommend > > adding visibility on how many donations were received and how it was > > distributed across relays. There should be safeguards to prevent > > oniontip.com from taking a part of the money, etc. > > > > Tom > > > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > Agreed, this is pretty awesome. It allows independent relay operators to > receive donations no matter where they are in the world whether or not > they are affiliated with any group. > > The donations are transparent, since the money can be followed on the > Bitcoin blockchain to ensure that your donation made it to the individual > addresses of the relay operators. > > > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays I like it! I've already made AUD $0.05!!! ;) M.

7 6

OnionTip.com distributes Bitcoin donations to all BTC addresses set in ContactInfo
by ban＠unseen.is 13 Aug '14

13 Aug '14

Hi, apparently this hasn't been discussed here yet. About a month ago, Donncha O'Cearbhaill build https://oniontip.com/ during the Dublin Bitcoin Hackathon. It is a webapp which automatically extracts all Bitcoin addresses set in the ContactInfo variable of the torrc and distributes Bitcoin donations based on the consensus weight. There are already 100+ relays listed which represent around 5% of the total consensus weight. In just a few weeks they distributed around 125 US$. There are many other theoretical ways to provide compensation to tor relay operators (see https://blog.torproject.org/blog/tor-incentives-research-roundup-goldstar-p…) but I really like this very simple and practical approach. Thoughts?

6 7

Re: [tor-relays] Contacting Apple About a Block IP Address
by Jesse Victors 13 Aug '14

13 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 I don't know about that. The number of site that ban all Tor nodes (exits and non-exits alike) is relatively low compared to the number of websites that don't. The banning happens when trigger-happy sysadmins think that 1) IP address == user, and 2) that banning all Tor nodes stops only spammers. Neither are true, but like Thomas said they probably just downloaded a list and banned all the nodes and didn't think about the 2.4 million Tor users. I've run relays from my own IP address with very little problems to speak of. Certainly you don't want to run an exit on your IP, that's a different story. Christopher, from another machine/IP, send a message to the admins of that forum and explain. Be polite, explain what error message you are seeing, and ask if your IP could be unbanned so that you can access their discussion forum as part of your work. You could also explain that Tor is an anonymity layer on top of TCP, and as your machine simply passes encrypted data through the Tor network and not out of it, it poses no risk of spam or abuse from anyone using Tor. If you feel that it's necessary, concisely explain what Tor is, pulling from descriptions on torproject.org. I think if your reasonable and work with them, you have a good chance of resolving this. If not, use a different IP for accessing the Apple forum. You can use an SSH tunnel, VPN, or a proxy if you need to. - -- Jesse V. On 08/13/2014 04:00 AM, tor-relays-request(a)lists.torproject.org wrote: > Don't run a relay from your own IP address. Pretty standard advice > there sorry regardless if it's an exit or non-exit. I guess the people > at Apple simply downloaded every Tor server IP and put no effort into > reading the differences between types of relay because to be fair, > they aren't paid to give a damn as long as it stops problems. > > You could pop an email off to their customer support, but honestly I > wouldn't get your hopes up with Apple. > > -T -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCQBmBQJT651rXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yAv9AH/0escYcwLAbUgbNRKCCQ0yY5 ugYHBnveTv6FIEPzDwPC/ZiinyQcc6IiYl+Qm6XfwavmHKkbMjDR2/OCjh53Mcop HIP9QcBQ/81ZdJCp9YH21FPnKozkzAAI3JNgVR0/0cRp/dd8EsARIN4lEWuHCXkE CfpCUuFNDHcv7OY3kgnd81byT034ZnoZFlJX3MJmVvpYmv+w/BIsUzd3jTEi2R6y /+ExKwbKc3d0LzHubv3E1Y54B1mIwF+5MbLn7jUYjv55/IDKvuBYTmInj50ygv7o AoRr+c0drDdoXahG14ltNtB9mbzMPmlStsWJ8q5AYSmqS8TJzcsXSNyT1y6QpPU= =XjfD -----END PGP SIGNATURE-----

4 3

Directory Server Issue
by Spencer Rhodes 13 Aug '14

13 Aug '14

Hi, I have a server (triratna) which I recently put up, which operates on ports 80 and 443, and which initially showed a Directory Server flag. After several days of operation, however, the directory flag disappeared from both the torstatus listing and from the arm display on the console. I would like to know if there is a way to verify that directory services are in fact working, and if so, determine why the server is not flagged properly. I found some old postings to the effect that one could browse to server://tor or server://tor/status/all, but this does not seem to be true any more. Thanks, Spencer Rhodes -- Spencer Rhodes, Esq. 126 East Jefferson Street, Orlando, Florida USA 32801-1830 t: +1.321.332.0407 | f: +1.321.332.0409 | m: +1.407.796.8282

2 1

Contacting Apple About a Block IP Address
by Christopher Burg 13 Aug '14

13 Aug '14

Hey fellow relay operators, While searching for a solution to a problem I've been having I learned that my IP has been blocked from accessing discussions.apple.com. The message that I get is the same message I get whenever I attempt to access a website known to block IP addresses operating Tor relays. I am running a non-exit relay, which I'm assuming is the reason I'm now blocked from access the site. Has anybody else run into this problem and, if so, have you been able to get your IP address unblocked by Apple? If you have managed to get your IP unblocked what steps did you take? Unfortunately due to my work I am in a position where I have to access Apple's discussion forums from time to time. Thanks, Christopher Burg

3 2

multisig link
by jason＠icetor.is 10 Aug '14

10 Aug '14

sorry meant to include relevant link to multisignature documentation https://github.com/bitcoin/bips/blob/master/bip-0010.mediawiki -J

1 0

Tor relay giving a OR_CONN_CLOSED error‏
by Richard Dennis 09 Aug '14

09 Aug '14

Hi guys, I created a tor relay set up using a raspberry pi called Goblin500, it has now been up for a while and i have the fast, valid, running and v2dir flag i have been working on some code that can be found at: https://github.com/richarddennis/Masters-Project to connect to various nodes in tor and create a stream, i am able to connect no problem to various nodes such as TorLand1, orion etc no problem, however when i try to create a circuit containing Goblin500, there is a significant delay and when i do receive anything it is only get a destroy cell containing the error code 8 - OR_CONN_CLOSED the node is in the consensus : r Goblin500 IspSUjBIQ/LJ0k18VbKIO6mS1oo yT+H3s9/UYm7p+BmNjnfYUmGHFw 2014-08-09 16:03:43 82.26.108.68 9001 9030s Fast Running V2Dir Validv Tor 0.2.4.23w Bandwidth=20 Unmeasured=1p reject 1-65535my torrc file is SocksPort 0/var/log/tor/debug.logRunAsDaemon 1ControlPort 9051CookieAuthentication 0ORPort 9001Nickname Goblin500DirPort 9030ExitPolicy reject *:* what is causing the error and more importantly how can it be solved there are no errors in the/var/log/tor/notices.log file Thanks Rich

1 0

New router, new IP address
by Rick 08 Aug '14

08 Aug '14

So I saw the Craigslist post in tor-talk and checked to find that I'm at full speed with them. Since I'm an exit relay (residential, US, 15 months) and have been experiencing the CL Dial-Up Retro for a few months, I was surprised. It turns out that I have a new IP address so for the moment I'm a shiny new exit. Two days ago I installed a new router. Nothing special: $45 Linksys but selected specifically for use with DD-WRT. ROM burn and set-up was done completely offline. It took maybe a minute to do the router hot swap and all went well. IP address change never crossed my mind. After all, I was down for four days back in the winter (ice storm) and hoping for a new address when we came back up. No luck. Is this normal? Or at least not unusual? It seems a bit spooky to me. I thought the address was tied to the cable modem (ISP's equipment) and they couldn't care less about my LAN. :-\ Thanks Rick

2 1