January 2018 - tor-relays - lists.torproject.org

Question: systematic hacking on my social media accounts
by Paul Templeton 14 Jan '18

14 Jan '18

Hi all, Just wondering if anyone else has had this problem over the last week. I have had attempts (one successful) on my social media accounts. Just found it strange that it was more than one. They got into my Facebook page (Haven't used it for years) - Seems that they got access via really old personal questions that family have provided them via their online posts - ie happy birthday now that you are this old... and hows your dog m#### doing and my mum listing her maiden name etc. I can't get it through to people to stop them from having public profiles... SIGH. Mean while they have to put up with girly pics or unfriend me as i'm not interested in the account. A lesson for all. Paul 609662E824251C283164243846C035C803940378

2 1

which countries in the world are missing a Tor Relay?
by Fabio Pietrosanti - Lists 13 Jan '18

13 Jan '18

I was wondering which countries in the world are missing a Tor Relay? It would be nice to have a small project reporting which countries are still missing Tor relays, to invite people to find a way to run at least one there, being exotic places or just unusual places! Fabio

6 5

request for comments: The Tor Relay Guide (Draft)
by nusenu 12 Jan '18

12 Jan '18

The #Tor relay documentation on www.torproject.org has shown its age and some of us have been working on writing something new, currently it lives on trac but will live on a website eventually. The Tor Relay Guide https://trac.torproject.org/projects/tor/wiki/TorRelayGuide It also features instructions to setup automatic package updates for multiple Linux distributions. I'd like to get your feedback! The preferred location is via email or on the trac ticket: https://trac.torproject.org/projects/tor/ticket/24497 thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

4 6

denetron.com Tor Relays MyFamily Configuration
by nusenu 12 Jan '18

12 Jan '18

Hello, thanks for running Tor 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. Some more background: https://hackernoon.com/some-tor-relays-you-might-want-to-avoid-5901597ad821 https://nusenu.github.io/OrNetStats/endtoend-correlation-groups Let us know if you need any help with this. thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

1 0

Faravahar - Scheduled Maintenance - Thursday, January 11, 2018 at 18:00:00 UTC to 22:00 UTC
by Sina Rabbani 11 Jan '18

11 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Scheduled Maintenance Thursday, January 11, 2018 at 18:00:00 UTC to 22:00 UTC Dear Tor Network, I am upgrading/replacing the hardware for Faravahar, and would like to announce a maintenance window: Scheduled Start: Thursday, January 11, 2018 at 18:00:00 Scheduled End: Thursday, January 11, 2018 at 22:00:00 During this event the server will be out of service and unavailable. I will reply to this email with updates when the work begins and upon completion. All the best, Sina -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJaVVAaAAoJEMeylP64yITyeR8P/jr13qhdtK/zWja9Ybp6NbBq +jWBSes/CGxLGtIRs/DIXF6jlhaPfM+yO/bhQ3MJvpa5ls50EPQhzEuUnbM3Zxtv 586cgclupXtDXyu8n7wbJRelmbRZ7Ef7mQDc9IaNU3J4UgzsS0bNghIKO1gfq2rc HK97JIqnGyPDjzrPvFatzdKWAkmIk6TR4c6zuCcHZqNChQxSkOge0acOo69fusL/ 4TQr69GOTklV6N3YVvo8OLzUlWNGGj1CHVN6nJD11NwyZFrQ6kC1PfaPcUNs0CUB ecge5FBXXFb1gDA9gr2THAdw++bmOZwaKKgqgyyU6qFhQkOHAnHhTh5Ef0YBIwXg l4m4FW+u91yfv2rHaXF2K4DgjhgKkjfmmsmT2NIIE7uCxtr8otmJQSyy6W8awn2Y ymoMUfCbqUD3QNUHU90PJmTSlzK2+Asp2cd8PdiIILXsmwVq+JBt09MnT/lDO/UH kxnNTK7VnVChpef40z1JyZKyGOeXc/a4O5VvyfvYDohe9sBiiINdfGz7RA6+BOsE ChUp8PiGimyWZpHVO7ccZyWya3mTT43HRJjr3U0LoZNBb1S/CwYre1B/7e2M3i/D WYOQc/ubTuw6ZOJ79QMxPdUR76WLsJi/ULZ1iqEwdyagg/jnUsDNMRYp4da12kij iESAh7F4Tom7zeh2xHh1 =qe70 -----END PGP SIGNATURE-----

1 2

Failing because we have 1354 connections already.Please read doc/TUNING for guidance.
by rush23＠gmx.net 10 Jan '18

10 Jan '18

2 1

Nyx reported speed
by John D. McDonnell 09 Jan '18

09 Jan '18

I'm not sure if reporting is off or something isn't configured right or whatever it could be, but when running nyx, it is telling me that the measured rate is 229.0 B/s which to me, sounds ridiculously slow. Where is it getting the measured rate from? Is it a calculation on how much data is passing in a given time or some sort of speed test from another relay or where? While I've used Tor off and on for several years, I never ran a relay until now and I'm still not certain on several aspects, though I keep digging to make sure I can supply the best exit relays I can. (I currently host 2 exit relays and hope to bring up 3 more in the near future if I can find hardware to run them on. Though I may make one a bridge.) I have some spare internet connections that are provided to us that are 25/5 connections. I configured torrc with a 500KB/s limit with 600KB/s bursting as this should work nicely to use ~4Mbps of the 5Mbps that the connection supports and allows me some bandwidth to be able to connect to the machines for monitoring and troubleshooting as well as more than enough bandwidth for downloading updates and such. The line in nyx that I'm referring to is: Bandwidth (limit: 500 KB/s, burst: 600 KB/s, measured: 229.0 B/s): Where is it getting that 229.0 B/s rate and is there anything I can do to get it closer to the 500KB/s I am trying to share. Granted, I am using a Linksys e1200 and Belkin something-or-other that I can't remember off the top of my head running DD-WRT as routers in front of the servers. (I've pondered removing the router and just connecting the server directly to the internet and relying on pf for my firewalling, but I can't do that at the one location as I also have a couple other things connected to it. Both routers are higher end consumer routers with 32MB of RAM and has 32768 for maximum ports. (Currently just under 3000 active IP connections as I'm typing this e-mail.) I might just try this on my one exit to see if this is the bottleneck I'm hitting or if there's something else affecting it. When I had first put this in place, I was using an older Netgear ProVPN router of some sort, but I swapped it out due to it flagging NTP traffic as unknown even though my server was initiating the NTP requests. But I was maintaining 200KB/s+ connections fairly consistently. It now ranges all over the place and I'm not sure if that's an issue on my end or just part of the lifecycle of a relay. I just recently rebooted the machine this happened to pop up in the nyx log window as I was looking at this: 12:33:09 [NOTICE] Heartbeat: Tor's uptime is 4 days 23:59 hours, with 1928 circuits open. I've sent 37.89 GB and received 37.00 GB. To me, that seems a too low, but I've not sat down to do the math and maybe that's a good statistic for 5 days at 4Mbps. I'd appreciate any tips and pointers you can send my way. And if the consumer routers are the issue, I can move my one exit relay to one of the other connections I have and not use it at the location (or just run one that's slower) where I do use this backup internet connection. (It's handy to have a network that's not part of our internal network for testing.) Thanks for sticking with me through this whole e-mail and I apologize for rambling and jumping around a bit. I'm sure I left out some stuff and didn't clarify something else or something wasn't clear, so if you need more information, just ask. Thank you, John Penn Cambria School District This e-mail and any files transmitted with it are confidential and intended only for the person or entity to which it is addressed. If you have received this email in error, please notify the sender immediately via email and delete this email along with any attachments from your system. Any unauthorized or improper disclosure, copying, distribution, or use of the contents of this e-mail and attached documents is strictly prohibited. The views and opinions of this email or attachments are reflections of the author and are not necessarily the views and opinions of Penn Cambria School District. We do not accept responsibility or liability for any loss or damage from the receipt of this email, its use, or for any errors or omissions. www.pcam.org<http://www.pcam.org>

3 8

Configuring your relay
by Tommy Collison 09 Jan '18

09 Jan '18

Hi there, I'm Tor's writer/editor. We just got a question on Twitter that I'm stumped on, and I had a quick look through the documentation and didn't find anything. Can anyone shed some light? - Can you set up a relay to provide more bandwidth during specified hours? (e.g. more at night, less during the day.) - Is there a way of configuring the relay to work only on certain days? I assume not, and that this would have to be done manually, maybe with cron? Cheers, TC

3 2

Relay not listed in atlas
by Fabian A. Santiago 09 Jan '18

09 Jan '18

One of my relays is no longer listed in atlas. I'm curious why and how can I go about examining the issue? It had been running for several weeks at this point seemingly fine. My other relay lists it as an alleged family member but it's id is listed in a different color (yellow). Is this part of the ddos issue I've seen spoken of here? The server is accessible and Tor is running. System stats look fine. Any ideas? Thanks. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

3 5

Updated Fallback Directory Mirrors
by teor 09 Jan '18

09 Jan '18

Dear Relay Operators, Thanks to everyone who opted-in their relays as fallback directory mirrors. We rebuilt the list of fallbacks on the weekend. [0] The new list will come out in Tor 0.3.2.9. It will be backported to all supported Tor releases. [1] The FallbackDir flags on Consensus Health [2] have been updated. The flags on Relay Search (Atlas) [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. You can keep replying to this thread to opt-in your relays. 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.) We are tracking fallback changes in this ticket [4]. 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.0, and 0.3.1. (0.2.5 doesn't have the fallback feature). 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://atlas.torproject.org/#details/001524DD403D729F08F7E5D77813EF12756CF… [4]: https://trac.torproject.org/projects/tor/ticket/24805 -- Tim / teor PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------

2 1