- tor-relays - lists.torproject.org

Re: [tor-relays] Detecting Network Attack [re: exit synflooded]
by tor＠t-3.net 25 Nov '17

25 Nov '17

I went and added a reject for exit to port 8888 and HUPed the process. Maybe this is the fix! :)

1 0

Exit from Different IP from OR Port
by Dr Gerard Bulger 25 Nov '17

25 Nov '17

Direct Exit to a different IP. I naively thought that the proxy lines in torrc could to that via an https proxy. Alas that's not what that line is for! I got an impression from earlier chats a while ago that exiting to a non-advertised IP was regarded as simply not cricket, in that the internet should know the IP or Tor exits exiting. The trouble now is too many are sites apply blanket bans on Tor exits. I failed get a Tor on my VPS to use a VPN as the final exit, as my knowledge of routing is too limited. I kept cutting myself off from the branch I was sitting on fiddling with this remotely. As some exits to do manage this, I wonder if anyone can post be a script or point me in the right direction as to how they do it. Scenario: Set up a VPN connection. Have a script that in effect offers split tunnelling for TOR to allow exit via the VPN. The OR port needs to remain local fixed IP. The default route of the VPN server remains local. Doing everything in and out via most VPNs would not be useful as these services have very dynamic IPs. Gerry >>>Detecting exit nodes is error prone, as you point out. Some exit >>> nodes have their traffic exit a different address than their >>> listening port. Hey does Exonerator handle these? >> Right. It's not trivial for tor to figure out what exit relays are >> multi-homed -- at least not without actually establishing circuits >> and fetching content over each exit relay. >> >> I just finished an exitmap scan and found 17 exit relays that exit >> from an IP address that is different from what's listed in the >> consensus: > This mode of operation, regardless of how it happens, is not in itself > a problem, nor cause for alarm. In fact, the nature of these "exit IP > different than ORPort" relays can and often does assist users in > circumventing censorship... a fundamental use case of Tor. > For instance, the arbitrary automated and blind blocking via dumb > blocklists that prevent even such most basic user activity and human > right to knowledge as simply reading websites via Tor. Such blocking > examples can often be found here: > https://trac.torproject.org/projects/tor/wiki/org/doc/ListOfServicesBl > ockingTor > > It's also entirely up to the exit operator to determine if the third > party non contractual / SLA exonerator service is of any particular > use or benefit to them or not... perhaps they have other notary means, > or are immune or not subject to any such legal or jurisdictional > issues, for which it becomes moot. > > Similarly, realtime TorDNSEL and the like could be considered to be > censorship enabling tools. > -----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: 25 November 2017 07:31 To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] Tor Metrics issue > On 25 Nov 2017, at 17:36, Arisbe <arisbe(a)cni.net> wrote: > > In the immediate past I monitored both my relays and my bridges through atlas. So, now with Tor Metrics, I don't see my bridges. Am I doing something wrong or are they not in the data base? How do you search for your relays and bridges? T _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

3 2

Pretty sure our exit was being synflooded.
by tor＠t-3.net 25 Nov '17

25 Nov '17

Was anyone else's exit being synflooded yesterday and today? I put some iptables code in to help, it might have mitigated it. I'm pretty sure our exit "Libero" was being synflooded. Managed to lose all our flags shortly after the instability was (finally) resolved, go figure =p

2 1

Re: [tor-relays] my IP got blocked -> closed
by Patrice 25 Nov '17

25 Nov '17

Hi, I want to tell that the issue is no longer exists. I can now visit ebay, ikea, ect. without a problem. It was like grarpamp said, there was a bunch of malicious software on one of my Computers. Very shameful, there was no virus detection installed. Therefore my tor relay was not the problem but my windows pc. ;-) Thank you for your help! Kind regards Kalle > 2. Re: my IP got blocked (grarpamp) > >>> Detecting exit nodes is error prone, as you point out. Some exit nodes >>> have their traffic exit a different address than their listening >>> port. Hey does Exonerator handle these? >> Right. It's not trivial for tor to figure out what exit relays are >> multi-homed -- at least not without actually establishing circuits and >> fetching content over each exit relay. >> >> I just finished an exitmap scan and found 17 >> exit relays that exit from >> an IP address that is different from what's listed in the consensus: > This mode of operation, regardless of how it happens, is not in > itself a problem, nor cause for alarm. In fact, the nature of these > "exit IP different than ORPort" relays can and often does assist > users in circumventing censorship... a fundamental use case of Tor. > For instance, the arbitrary automated and blind blocking via dumb > blocklists that prevent even such most basic user activity and human > right to knowledge as simply reading websites via Tor. Such blocking > examples can often be found here: > https://trac.torproject.org/projects/tor/wiki/org/doc/ListOfServicesBlockin… > > It's also entirely up to the exit operator to determine if the > third party non contractual / SLA exonerator service is of any > particular use or benefit to them or not... perhaps they have other > notary means, or are immune or not subject to any such legal or > jurisdictional issues, for which it becomes moot. > > Similarly, realtime TorDNSEL and the like could be considered > to be censorship enabling tools. >

1 0

Re: [tor-relays] Pretty sure our exit was being synflooded.
by Paul Templeton 25 Nov '17

25 Nov '17

Happening to middles as well - I get black hold all the time - ISP has auto rules. Paul ----- Original Message ----- From: tor(a)t-3.net To: tor-relays(a)lists.torproject.org Sent: Saturday, November 25, 2017 10:23:24 AM Subject: [tor-relays] Pretty sure our exit was being synflooded. Was anyone else's exit being synflooded yesterday and today? I put some iptables code in to help, it might have mitigated it. I'm pretty sure our exit "Libero" was being synflooded. Managed to lose all our flags shortly after the instability was (finally) resolved, go figure =p _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Tor meetup at Primavera hacker (Santiago de Chile) [es/en/pt]
by ilv＠torproject.org 22 Nov '17

22 Nov '17

[ES][EN][PT]¡Encuentro Tor en la Primavera Hacker! ¡Ven! ======================================================== [ES] ¡Encuentro Tor en la Primavera Hacker! ¡Ven! [EN] Tor Meetup at Primavera Hacker! Join us! [PT] Encontro Tor na Primavera Hacker! Venha! [ES] ¡Encuentro Tor en la Primavera Hacker! ¡Ven! ------------------------------------------------- ¡Hola! La Primavera Hacker está por llegar. Durante los días 2 y 3 de diciembre, hackers, activistas, tecnólogos, feministas y demás fauna se darán cita en Santiago de Chile. Esta es una invitación para todos los interesadas e interesados en colaborar con la comunidad Tor. Tor es software libre, estructurado alrededor de una red de servidores mantenidos por voluntarias y voluntarios a lo largo del globo para proteger el anonimato en línea y evadir la censura en Internet. Durante los dos días, miembros de la comunidad Tor estarán presentes en la Primavera Hacker con agenda abierta, dispuestos a conversar, intercambiar experiencias, aprender y enseñar respecto a las tecnologías contra la vigilancia y, principalmente, discutir sobre cómo colaborar con Tor. Tendremos también una mesa llena de stickers y regalitos de Tor :-) Encuentro Tor ------------- La red Tor está compuesta por más de 6 mil computadoras alrededor del mundo. Sin embargo, América Latina tiene una participación muy pequeña. Actualmente en Chile hay solamente 2 nodos en funcionamiento. En Brasil, apenas 25. ¡Necesitamos aumentar la diversidad de la red más allá de los Estados Unidos y Europa! Ven y participa del Encuentro Tor, y aprende como ser parte de la comunidad. Durante los dos días del festival, nuestra idea es cubrir los siguientes temas: - Como funciona Tor, por qué Tor tiene problemas con los VPNs y con los servicios proxy de un salto (1-hop) - Install fest: ¡Instala Tor Browser y Orbot con nosotros! - Como colaborar con la traducción de la documentación al castellano. - Como instalar, configurar y administrar su nodo de Tor. - Como ser voluntario más allá de mantener nodos. - Como usar OONI para detectar la censura en redes. - Como usar herramientas como onion-share. - Tor en universidades y buenas prácticas de investigación. - Tor y la ley, ajustar la legislación sobre Tor en Latinoamérica. - Mejorar la metodología de pruebas para OONI -- Listas de URLs de prueba (https://ooni.torproject.org/get-involved/contribute-test-lists/) - OONI y bloqueos: Cómo analizar los datos de OONI (https://api.ooni.lo) Si no puedes llegar al encuentro, puedes hablar por el canal: IRC: irc.oftc.net #tor-south Por la lista de correo: https://lists.torproject.org/pipermail/global-south/ Y el Wiki (Trac) para la documentación, eventos y otras cosas: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje… Primavera Hacker: https://phacker.org - http://u5ed42u6sbzq7xzs.onion Un abrazo, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- [EN] Tor Meetup at Primavera Hacker! Join us! Hi! Primavera Hacker (Hacker Spring) is coming. During December 2 and 3, hackers, activists, technologists, feminists and related people will meet in Santiago de Chile. This is an invitation for all people interested in collaborating with the Tor community. Tor is free software, structured around a network of volunteer-run servers, spread all around the world to anonymity online and circumvent Internet censorship. During the two days of the meeting, Tor community members will be present at Primavera Hacker with an open schedule, eager to tealk, exchange experiences, learn and teach about technologies against surveillance and, mainly, discuss how to collaborate with Tor. We will also have a table full of stickers and other Tor swag :-) Tor Meetup ---------- The Tor network is formed by over 6 thousand computers around the world. However, Latin America hosts a very small share of it. Nowadays, in Chile there are only 2 working servers. In Brasil, just 25. We need to increase the diversity of the network beyond the United States and Europe! Come and be a part of the Tor Meetup, and learn how to engage in the Tor community. During the two days of primavera hacker we will cover the following topics: - How does Tor work, why does Tor have problems with VPNs and 1-hop proxy services. - Install fest: Install Tor Browser and Orbot with us! - How to collaborate translating documentation into Spanish. - How to install, configure and administer your Tor relay. - How to use OONI to detect network censorship. - How to use tools such as onion-share. - Tor for universities and good research practices. - Tor and the law, adjust legislation about Tor in Latin America. - Improve the OONI testing methodology -- List of test URLs (https://ooni.torproject.org/get-involved/contribute-test-lists/) - OONI and blocking: How to analyze OONI data (https://api.ooni.lo) If you cannot make it to the meeting, you can talk with the participants on the following channel: IRC: irc.oftc.net #tor-south On our mailing list: https://lists.torproject.org/pipermail/global-south/ And the Wiki (Trac) for documentation, events and other things: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje… Primavera Hacker: https://phacker.org - http://u5ed42u6sbzq7xzs.onion hugs, ==== Encontro Tor na Primavera Hacker! Venha! ======================================== Hola! A Primavera Hacker está chegando! Nos dias 2 e 3 de dezembro, hackers, ativistas, tecnologistas, feministas se encontrarão em Santiago, no Chile. Este é um convite para todos interessados e interessadas em colaborar com a comunidade Tor. O Tor é um software livre rodado por uma rede de servidores voluntários distribuída pelo mundo para garantir o anonimato online e contornar a censura na Internet. Durante os dois dias membros da comunidade Tor estarão presentes na Primavera Hacker com a agenda aberta para conversar, trocar experiências, aprender e ensinar as tecnologias anti vigilância e, principalmente, discutir sobre como colaborar com o Tor. Teremos uma mesa cheia de adesivos e brindes do Tor :) Encontro Tor ------------- A rede Tor é composta por mais de 6 mil computadores ao redor do mundo. No entanto, a América Latina tem uma participação muito pequena. Atualmente, no Chile há apenas 2 servidores em funcionamento. E no Brasil apenas 25. Nós precisamos aumentar a diversidade da rede além dos Estados Unidos e Europa! Venha participar do Encuentro Tor e saiba como se engajar na comunidade Tor. Durante os dois dias a nossa ideia é ensinar: - Como funciona o Tor, porque Tor, os problemas com as VPNs e serviços proxy de 1-hop. - Install fest: instale Tor browser & Orbot com a gente! - Como colaborar na tradução da documentação em ES/PT. - Como instalar, configurar e gerenciar o seu relay do Tor. - Como usar o OONI para detectar a censura na rede. - Como usar ferramentas como onion-share. - Como ser voluntário além da hospedagem de servidores. - Tor em universidades e boas práticas de pesquisa. - Tor e a lei: ajustar as leis para o Tor na América Latina. - OONI melhorar a metodologia testada -- listas de URL de testes (https://ooni.torproject.org/get-involved/contribute-test-lists/) - OONI e bloqueios, como analisar OONI data (https://api.ooni.io) Se você não puder comparecer no Encontro, você pode falar com a gente por esse canal: IRC: irc.oftc.net #tor-south E pela lista de email: https://lists.torproject.org/pipermail/global-south/ E wiki (Trac) para documentacao, eventos e outras coisas: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje… Primavera Hacker: https://phacker.org - http://u5ed42u6sbzq7xzs.onion um abraço, -- ilv, gus, vasilis, gwolf

1 0

The Onion Box v4.0
by Ralph Wetzel 18 Nov '17

18 Nov '17

3 3

Re: [tor-relays] [tor-dev] Detecting multi-homed exit relays (was: Onion auto-redirects using Alt-Svc HTTP header)
by grarpamp 18 Nov '17

18 Nov '17

>> Detecting exit nodes is error prone, as you point out. Some exit nodes >> have their traffic exit a different address than their listening >> port. Hey does Exonerator handle these? > > Right. It's not trivial for tor to figure out what exit relays are > multi-homed -- at least not without actually establishing circuits and > fetching content over each exit relay. > > I just finished an exitmap scan and found 17 > exit relays that exit from > an IP address that is different from what's listed in the consensus: This mode of operation, regardless of how it happens, is not in itself a problem, nor cause for alarm. In fact, the nature of these "exit IP different than ORPort" relays can and often does assist users in circumventing censorship... a fundamental use case of Tor. For instance, the arbitrary automated and blind blocking via dumb blocklists that prevent even such most basic user activity and human right to knowledge as simply reading websites via Tor. Such blocking examples can often be found here: https://trac.torproject.org/projects/tor/wiki/org/doc/ListOfServicesBlockin… It's also entirely up to the exit operator to determine if the third party non contractual / SLA exonerator service is of any particular use or benefit to them or not... perhaps they have other notary means, or are immune or not subject to any such legal or jurisdictional issues, for which it becomes moot. Similarly, realtime TorDNSEL and the like could be considered to be censorship enabling tools.

1 0

my IP got blocked
by Patrice 18 Nov '17

18 Nov '17

Hi everyone, I`ve got an issue with my local IP address. I am running a relay about 1 year and since 3 or 4 weeks I can`t reach some websites like: ebay or ikea. All I get is this message: * * *Access Denied* You don`t have permission to access "Http://www.ebay.com/" on this server. Reference # ____looong number______ I think I am on some blacklists. After I change my IP address all worked fine for only 2 days. Can I do something about this? Thank you for your help! Kind regards Kalle

7 7

Re: [tor-relays] tor-relays Digest, Vol 82, Issue 25
by Gabriel Curtis 16 Nov '17

16 Nov '17

tor-relays-request(a)lists.torproject.org On Nov 16, 2017 3:22 AM, <tor-relays-request(a)lists.torproject.org> wrote: > 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. Re: Atlas is now Relay Search! (teor) > 2. Test (Alessandro Lo Mo) > 3. Re: Test (Paul Templeton) > 4. Re: Atlas is now Relay Search! (Iain R. Learmonth) > 5. Re: Atlas is now Relay Search! (r1610091651) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 16 Nov 2017 13:36:52 +1100 > From: teor <teor2345(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Atlas is now Relay Search! > Message-ID: <FA8F2762-65E0-430B-BAE1-E3B45827A464(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > > > On 15 Nov 2017, at 09:26, Iain R. Learmonth <irl(a)torproject.org> wrote: > > > > On 14/11/17 18:26, teor wrote: > >> No, it isn't: one of the new resources appears to be blocked by AdBlock > >> Plus for iOS. So it only works with content blockers turned off. You > probably > >> want to fix this eventually, because these blocklists are popular. And > the > >> issue likely affects multiple platforms. But it's not an all iOS > devices bug. > > > > I've tested with AdBlock Plus in Firefox and I cannot recreate this > problem. > > > > Can you tell me what resource it is that is blocked and what rule it is > > matching? > > No, I can't, because iOS ad blockers do not provide this information. > Did you add many resources in the transition? > > T > > -- > Tim / teor > > PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B > ricochet:ekmygaiu4rzgsk6n > ------------------------------------------------------------------------ > >

1 0

Atlas is now Relay Search!
by Iain R. Learmonth 16 Nov '17

16 Nov '17

Hi All, You may notice that Atlas has a new look, and is no longer called Atlas. For now no URLs have changed but this is part of work to merge this tool into the Tor Metrics website. The style is determined by the Tor Metrics Style, and modifications have been made to fit this. The decision was made to deploy these changes before the actual integration into metrics.torproject.org to allow for other issues to be worked on. This was a big change and it was tricky maintaining two branches of the codebase. Issues should still be reported on the Metrics/Atlas component in the Tor trac if they arise. When we come to full integration, URLs will change but there will be a period where we maintain redirects to prevent any URLs from breaking while waiting for being updated. Thanks, Iain.

13 30

Test
by Alessandro Lo Mo 16 Nov '17

16 Nov '17

Test

2 1

Re: [tor-relays] Atlas is now Relay Search!
by Arisbe 15 Nov '17

15 Nov '17

Hello All, I use to review my bridges as well as my relays on Atlas. Now I don't find my bridges on nyx. Is this something I'm doing wrong?

2 1

Re: [tor-relays] tor-relays Digest, Vol 82, Issue 23
by Patrice 14 Nov '17

14 Nov '17

How do I use a different IP address? I only got one. Should I pipe the traffic through a proxy (somewhere else)? Yeah, I though about to use the Tor browser but for my girlfriend I think not. Kind regards Kalle >> After reading all the answers, there seem to be only two solutions: >> 1. hoping that my IP get unbanned >> 2. shutdown the relay > Use a separate IP address for the relay > Run a bridge > >> (3. surf over a proxy or VPN) > Use Tor Browser? :-) > > T

2 1

Re: [tor-relays] Atlas is now Relay Search!
by Ralph Seichter 14 Nov '17

14 Nov '17

On 14.11.17 16:42, Artur Pedziwilk wrote: > Works OK on my Safari Version 11.0.1 (13604.3.5) and macOS 10.13.1 (17B48). Same versions here, but Relay Search does not work for me. URLs that are supposed to show node details don't work either, only the broken query page is shown. I tested this both with existing Atlas bookmarks and URLs copied over from Chrome. -Ralph

3 3

Re: [tor-relays] my IP got blocked
by Patrice 14 Nov '17

14 Nov '17

Sadly I run a only a relay therefore this is a troublesome action. So if more admins do this, I could be in trouble. After reading all the answers, there seem to be only two solutions: 1. hoping that my IP get unbanned 2. shutdown the relay (3. surf over a proxy or VPN) Kind regards Kalle >> Hi everyone, >> >> >> I`ve got an issue with my local IP address. I am running a relay about 1 >> year and since 3 or 4 weeks I can`t reach some websites like: ebay or ikea. >> >> All I get is this message: >> >> * >> * >> >> *Access Denied* >> You don`t have permission to access "Http://www.ebay.com/" on this server. >> >> Reference # ____looong number______ >> >> >> I think I am on some blacklists. After I change my IP address all worked >> fine for only 2 days. >> >> Can I do something about this? >> >> Thank you for your help! >> >> Kind regards >> Kalle >> > If you're running an exit, they probably saw abusive traffic, didn't > like it, and blocked your IP. You could consider not running an exit > relay from home. > > If you're running a non-exit, then they're being dumb for blocking your > IP when it is impossible for abusive traffic to come from your relay. > Some webmasters who don't understand Tor do that, but there's not really > anything we can do. Best I can suggest is you try talking to them, which > isn't a very satisfying suggestion, I know. > > Matt >

2 1

HS and relay - same server different tor instance
by blaze glory 14 Nov '17

14 Nov '17

2 2

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