tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

PSA: exclude /var/lib/tor/diff-cache/ from your backups
by Roman Mamedov 14 Nov '17

14 Nov '17

Hello, Turns out that dir is highly variable, and judging from the name, also disposable. In my case it was responsible for about 20 GB of churn over a month, i.e. it took 25 GB to keep incremental backups of two Tor nodes with only 2 GB each in root FS (and I was wondering what's going on with my backup location's free space...) Dear Tor project: this is very bad style to keep that in /var/lib, content with properties like this must go into /var/cache/ [1], where it would be automatically excluded from backups by default policies in most backup systems. [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#VARCACHEAPPLICATIONCACHEDATA -- With respect, Roman

3 2

Tor 0.3.2.4-alpha - debian packages available (important for fast exits)
by nusenu 13 Nov '17

13 Nov '17

If you are running a fast tor exit relay this fix is especially relevant for you: Nick Mathewson: > o Major bugfixes (exit relays, DNS): > - Fix an issue causing DNS to fail on high-bandwidth exit nodes, > making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on > 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for > identifying and finding a workaround to this bug and to Moritz, > Arthur Edelstein, and Roger for helping to track it down and > analyze it. Debian packages are available via deb.torproject.org now. If you want to stay with stable releases have a look at the following resolv.conf options: https://trac.torproject.org/projects/tor/wiki/doc/DnsResolver#Tuningeventdn… -- https://mastodon.social/@nusenu twitter: @nusenu_

1 1

New on relays and Tor
by Alfredo Bollati 13 Nov '17

13 Nov '17

Hi all I just started investigating and getting involved with Tor project. I have configured my router to port forwarding on one of its ports. Is there a way or some steps to follow in order to confirm that my bandwidth is being used by the relay? I have checked and the port it's open. Thanks -- Alfredo Bollati

6 5

OVH down
by Florentin Rochet 09 Nov '17

09 Nov '17

Hi all, A quick look this morning (UTC+1) at AS16276 (https://atlas.torproject.org/#search/as:AS16276) is a good example why we need more network diversity :-)

2 1

Exit Node Checking
by Kijani 08 Nov '17

08 Nov '17

Hi folks, Does anyone have a script for periodically updating strick exit nodes lists after running an inspection as per https://tc.gtisc.gatech.edu/bss/2014/r/spoiled-onions-slides.pdf or similar? Looking to help protect against crypto transaction sender redirect attacks. Many thanks

4 3

Re: [tor-relays] Nyx 2.0 Release
by Damian Johnson 07 Nov '17

07 Nov '17

Hi Stephanie, will this do the trick? http://blog.atagar.com/nyx-release-2-0/ On Tue, Nov 7, 2017 at 10:02 AM, Stephanie Whited <steph(a)torproject.org> wrote: > Glad we'll have a post up about this! > > Damian, do you want to write a draft and we can help polish or would you > like Tommy to write a draft first and get your feedback? > > -Steph > > > On 11/7/17 9:56 AM, Damian Johnson wrote: > > Thanks Tommy! Actually, I was just about to reach out to Stephanie to > ask how she would care to proceed with a tor blog post. Love to have > your professional touch on this Tommy. :P > > Cheers! -Damian > > On Tue, Nov 7, 2017 at 9:51 AM, Tommy Collison <tommyc(a)torproject.org> > wrote: > > Congrats on the launch, Damian! > > Want to write up something quick for the blog? If you want, I can pull > something together and run it by you. > > Tommy > > On 11/6/17 3:41 PM, Damian Johnson wrote: > > Hi all, after years of being in the works I'm pleased to announce Nyx! > A long overdue modernization of arm. > > http://blog.atagar.com/nyx-release-2-0/ > https://nyx.torproject.org/ > > Even more important for our controller space at large, Nyx is coming > hand-in-hand with Stem 1.6. A full year of improvements that include > descriptor creation support, ed25519 certificates, performance tuning, > and much, much more... > > https://stem.torproject.org/change_log.html#version-1-6 > > Cheers! -Damian > _______________________________________________ > 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 > > > -- > Stephanie A. Whited > Communications Director > The Tor Project

3 5

Testers needed for Nyx beta release
by Damian Johnson 07 Nov '17

07 Nov '17

Hi all! After five years Nyx (previously known as arm) is getting a far belated update. Under the covers the whole codebase has been rewritten from scratch, but for users things look much the same. One of those cases where... "When you do things right, people won't be sure you've done anything at all." -Futurama Main changes are... * Python 3.x support. * New website: https://nyx.torproject.org/ * Bandwidth graph now prepopulates when you start up, so you have a graph right away. * Connections are now available without togging DisableDebuggerAttachment in your torrc. * Support for showing IPv6 connections. * Dialog for picking tor events to log, rather than an arcane letter flag input. * Improved efficiency of log deduplication by multiple orders of magnitude. As such verbose logs no longer peg your CPU. * Richer control interpreter, including a python prompt like IDLE. * Removed features that frequently confused users such as the relay setup wizard and torrc validation. * Modernized dependencies. Nyx now uses Stem rather than TorCtl (which was deprecated in 2011). Our ducks should finally be in a row for release, but this being a full rewrite I'd like to start with an open beta to work out anything I might have missed. Would relay operators mind giving Nyx a whirl? To give it a try simply ensure you have a control port available in your torrc... ControlPort 9051 CookieAuthentication 1 ... and run the following... % git clone https://git.torproject.org/stem.git % git clone https://git.torproject.org/nyx.git % cd nyx/ % ln -s ../stem/stem stem % ./run_nyx Thanks! -Damian

17 71

Nyx 2.0 Release
by Damian Johnson 07 Nov '17

07 Nov '17

Hi all, after years of being in the works I'm pleased to announce Nyx! A long overdue modernization of arm. http://blog.atagar.com/nyx-release-2-0/ https://nyx.torproject.org/ Even more important for our controller space at large, Nyx is coming hand-in-hand with Stem 1.6. A full year of improvements that include descriptor creation support, ed25519 certificates, performance tuning, and much, much more... https://stem.torproject.org/change_log.html#version-1-6 Cheers! -Damian

4 5

Running both Transmission server and Tor relay
by Ch1keen 06 Nov '17

06 Nov '17

Transmission is the open source torrent application which supports web-based interface. So when users upload torrent files from other computers to that server, it automatically downloads files written in torrent files. I used that at my home server, but I'd like to use my server as Tor relay also. But as many knows, running BitTorrent over Tor is really bad idea. It seriously harms security of Tor network. So I thought about the solution about how to use them simultaneously. 1. One machine, Two services. If that situation not harms the security, I will use them on one machine. 2. Two machines, Two services. Running that services one machine to one service to avoid the crashes between two. 3. Gave up running one service. If really no way to run both, I will gave up running Transmission service. Which could be best solution I will make? Sent from ProtonMail mobile

5 6

handling of MyFamily for an outdated relay
by Toralf Förster 04 Nov '17

04 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Looking at his : I do wonder how to deal with deleting all /var/lib/tor/data2/* files of a Tor relay and running a new one with the same config (but now different key/fingerprint). I added the new fingerprint to the config, which now has 3 entries (the middle is 1 outdated): MyFamily 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA,6EABEBF38CE7E3DF672C4DB01383606FE3EB2215,D11D11877769B9E617537B4B46BFB92B443DE33D Is this the right way ? I'm asking b/c I do see now "Alleged Family Members" here: https://atlas.torproject.org/#details/D11D11877769B9E617537B4B46BFB92B443DE… - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWf3YchccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTuLJAQCAmqnYRI5y4NpShgQp7kcdSTC2 MfrsfHkH3aObifTJ1wD9ERBkJN6zAIY7usN6sPy4VfHzAjkGaMTDLoBlYRA2f1w= =EQTO -----END PGP SIGNATURE-----

2 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays