- tor-relays - lists.torproject.org

relayor v0.4.0 is released
by nusenu 01 Jul '18

01 Jul '18

Hi, relayor v0.4.0 is released. relayor helps you with running relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor This release contains important changes for exit operators that define their own exit policy, please _do_ read the changelog if you are an exit operator using relayor _before_ upgrading since it requires a minor configuration adjustment. If you do not change the default value for tor_ExitPolicy no configuration change is required. Changes since v0.3.3: ------------------------------ - major: change the format of tor_ExitPolicy (single-line to multi-line) previously it you defined the exit policy like: tor_ExitPolicy: "accept *:80, accept *:443, accept *:22" now you define your exit policy like this: tor_ExitPolicy: - accept *:80 - accept *:443 - accept *:22 - support multiple IP addresses for OutboundBindAddressExit - add support for OpenBSD 6.3 (drop 6.2) - add support for Ubuntu 18.04 (drop 16.04) - add support for Fedora 28 (drop 27) - drop support for Debian 8 and HBSD - increase min. tor version to 0.2.9.x - increase min. ansible verstion to 0.2.5.3 - add support for custom addition to MyFamily members - switch tor_alpha_version from 0.3.3.x to 0.3.4.x - Debian: switch to HTTPS (from HTTP) for repository traffic - reorder some torrc items Main benefits for a tor relay operator ====================================== * automation - no more manual setup tasks * security: offline Ed25519 master keys every tor instance is run with a distinct user * automatically makes use of IPv6 IPs (if available) * automatic tor instance generation (two by default - configurable) * enables tor's Sandbox feature by default on Debian-based systems * easily choose between alpha/non-alpha releases * easily restore a relay setup * easily choose between exit relay/non-exit relay mode * automatic deployment of a tor exit notice html page via tor's DirPort * automatic MyFamily management Supported Operating Systems ---------------------------- Debian 9 and Debian Testing OpenBSD 6.3 FreeBSD 10.4, 11.1 Ubuntu 18.04 CentOS 7 Fedora 28 regards, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

1 1

fix this please
by I 30 Jun '18

30 Jun '18

3 5

Gentoo's Github hacked
by I 29 Jun '18

29 Jun '18

1 0

Tor Exit Node Winter Shutdown
by Jason Odoom 29 Jun '18

29 Jun '18

Hello relay operators, I regret to inform you all that I will be shutting down my Tor Exit node - Winter [0] after more than five years. Digital Ocean's new bandwidth policy has made it incredibly expensive to keep this online. I incurred almost $200 of usage. I was lucky enough to have received a deduction off of my bill. I also believe that in this case asking for donations will do little to help. I did not host this Exit node for accolade but because I truly believe in what the Tor project is doing. I will allocate my budget for the Exit node towards monthly contributions to Tor as an alternative. Hopefully in the future I will be able to return. It's been fun. 0: https://metrics.torproject.org/rs.html#details/9EC5E097663862DF861A18C32B37… Best, Jason - Jason Odoom GPG 9031B50D

2 2

A general question for relay operators
by arisbe 29 Jun '18

29 Jun '18

Hello George and all, When I was learning to implement Tor I had difficulty wading through the web pages for information. Some pages were obsolete, some poorly maintained (think Tor flow or good/bad hosting companies). The Tor manual is just a huge list of Tor terminology with no aids to help find things. The Tor project site has no site map. I still occasionally have the same problems when I try to find something. I found this very discouraging as I tried to grow my first Tor node without a live person to help me. I can imagine how daunting this would be to someone also trying to learn linux. Hey, thanks so much for asking. I appreciate your interest.

3 3

No IPv6 bridges from bridges.torproject.org
by Roman Mamedov 28 Jun '18

28 Jun '18

Hello, If you select "Do you need IPv6 addresses - Yes", it always results in an error "There aren't any bridges available". No matter if choosing obfs4 or none for the pluggable transport. Is that thing working? There should be at least one available (with obfs4, too), or at least I was under impression that I run one. As a side note, that page always loads in my native language with no way to switch to English -- pages which do this are the worst. In this case it means I can't usefully copy-paste you the exact error messages that I get. -- With respect, Roman

2 1

Is Tor-network protected from using one hop?
by dave levi 27 Jun '18

27 Jun '18

I'm testing few things in Tor and I noticed that if im changing(from the source code) the number of hop's(nodes) to be more then 3 hop's it work's fine(slowly, but still working) and if im sting only 2 hop's its still works great. but, when i'm setting only 1 hop, i can open the Tor-browser but i can't use it(Tor-browser) to visit site(regular site or onion site too). so im thinking maybe the Tor-network have protected from users who are using 1 hop?

6 6

Re: [tor-relays] tor-relays Digest, Vol 89, Issue 49
by dave levi 26 Jun '18

26 Jun '18

first, Thank you all for you answers and help. let me make it a bit harder. now, im running a relay which is Guard and Exit relays. i have defined in my relay(the server that's running the relay in /torrc file) to be "AllowSingleHopExits 1" and set in my computer that running the TOR(in /torrc file) with the 1(one) hop to: "ExcludeSingleHopRelays 0" and "AllowSingleHopCircuits 1" so now every thing needs to be ok right? but, still its not working On Tue, Jun 26, 2018 at 5:34 PM, <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. Is Tor-network protected from using one hop? (dave levi) > 2. Re: Is Tor-network protected from using one hop? (Logforme) > 3. Re: Is Tor-network protected from using one hop? (Matt Traudt) > 4. Re: Is Tor-network protected from using one hop? (Nagaev Boris) > 5. Re: Is Tor-network protected from using one hop? > (Roger Dingledine) > 6. Re: Is Tor-network protected from using one hop? (Matt Traudt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 26 Jun 2018 17:16:46 +0300 > From: dave levi <levi72827(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] Is Tor-network protected from using one hop? > Message-ID: > <CAJUku5hQa5JCk1UCn_CynyVG=kxhXkQpC0-ApW=k7vJxPrTM5g@ > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I'm testing few things in Tor and I noticed that if im changing(from the > source code) the number of hop's(nodes) to be more then 3 hop's it work's > fine(slowly, but still working) and if im sting only 2 hop's its still > works great. but, when i'm setting only 1 hop, i can open the Tor-browser > but i can't use it(Tor-browser) to visit site(regular site or onion site > too). so im thinking maybe the Tor-network have protected from users who > are using 1 hop? >

2 1

bridge installation help please
by I 26 Jun '18

26 Jun '18

4 11

Relay Guide - IPv6 Connectivity Testing
by Matthew Finkel 25 Jun '18

25 Jun '18

Over the last few days I've started thinking more about IPv6 and, inevitably, I started thinking about how we can improve support within the Tor network. Within the last few months, there were a few instances of relay operators seeking answers for why their relay did not have the running flag in the consensus. After some investigation, in some cases this was because the relay had an IPv6 ORPort configured but a majority of the IPv6-enabled directory authorities did not believe it was running. Unfortunately, despite IPv6 connectivity being a necessity now, ISP rollout is slow and on-going in some geographical areas and network peering arrangements are sometimes sub-standard or not stable. The Relay Guide[0] has a section describing how an operator can enable an IPv6 ORPort, and there's a supplementary page[1] specifically describing additional information about it. Considering there are potential critical failures when the IPv6 ORPort is configured, should the relay guide suggest the operator confirm they have IPv6 connectivity to all of the IPv6-enabled directory authorities[2] before enabling it ("Please ping6/telnet/nc to these hosts before enabling this.")? It would also be nice if the relay, itself, performed self-checks of this connectivity and printed a warning log if some failure-threshold is reached (and possibly disabling the IPv6 ORPort). But, in reality, this is a hack around a broken internet - and I hesitate advocating for something like this in tor. Maybe there is a compromise we can find between the relay operator manually testing connectivity periodically and tor automatically doing-smart-things. Thoughts? - Matt [0] https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#IPv6 [1] https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto [2] https://gitweb.torproject.org/tor.git/tree/src/or/auth_dirs.inc

3 5