- tor-relays - lists.torproject.org

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9
by Mick 09 Feb '17

09 Feb '17

Sorry, I thought I had. I must have hit the wrong reply button. Now copied in. Apologies for the top post.......On 9 Feb 2017 21:58, Roger Dingledine wrote: > > On Thu, Feb 09, 2017 at 09:57:03PM +0000, mick wrote: > > Done > > > > Now running 0.2.9.9. > > Thanks! Can you send this to the list too, for completeness? > > Or, do you mind if I do that? > > --Roger >

1 0

Hostname in DirAuthority config
by Andrew Smith 09 Feb '17

09 Feb '17

Hi I'm experimenting running my own tor network. To achieve this I'm setting DirAuthority in torrc. But it seems that I cannot use a hostname for my DirAuthority. For example: DirAuthority da1 orport=7000 no-v2 v3ident=xxx da1:7000 xxx Results in the error: Unrecognized flag 'da1:7000' on DirAuthority line If I replace "da1" with an IP address there is no error. Is this expected behaviour? I'm running tor v0.2.8.12. The documentation calls this an "address" (as opposed to other parts which refer to an "IP") which made me think a hostname would work. Thanks -- Andy Smith http://andrewmichaelsmith.com | @bingleybeep

3 6

What does this log message mean ? : Starting with guard context "default"
by Toralf Förster 08 Feb '17

08 Feb '17

3 3

assign_to_cpuworker failed
by diffusae 07 Feb '17

07 Feb '17

Hello! What does this warning mean? "Jan 13 09:31:49.000 [warn] assign_to_cpuworker failed. Ignoring." Do I need to reduce the number of connection to the relay or could I ignore this message? Regards,

5 21

no ipv6 traffic from/to relays ?
by Toralf Förster 07 Feb '17

07 Feb '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Switching from 0.2.9.9 to 0.3.0.3-alpha now let 1/3 of my outgoing network traffic to exit ports (of my Tor exit relay) being ipv6. OTOH there's more or less no ipv6 traffic from/to other relays. Is this (another ipv6) bug/issue in Tor or just expected ? - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAliWTYAXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U7R/QD+Nr4q1CHmhVKgrUrqSp/fEXCEnLnpSfO+njxRdnICbOIA+wSwB02bIOgB mWS13po62pXdO8r3QJiiz5Q7G8ryvtkt =1Mzz -----END PGP SIGNATURE-----

4 8

Re: [tor-relays] [OrNetRadar] AS: "2267921 ONTARIO LTD" - Linux (6)
by nusenu 06 Feb '17

06 Feb '17

> New relays added on 2017-02-01 in AS "2267921 ONTARIO LTD" > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | CC | ORp | Dirp |Version | ContactInfo | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 |01:02:35| 64.137.243.13 | ca | 9001 | 9030 |0.2.8.8 | noah.holland(a)aol.com | phenomenamomentaryh | 1 > 1 | 0 |02:24:58| 64.137.172.121 | ca | 9001 | 9030 |0.2.8.8 | enriquehanson56(a)gmail.com | UwFrNxQgYtBeMv | 1 > 1 | 0 |04:10:09| 45.62.244.240 | ca | 9001 | 9030 |0.2.8.8 | kmjapiji(a)mail.com | 9U5Cs7gu3XTORY | 1 > 1 | 0 |04:17:13| 45.62.252.66 | ca | 9001 | 9030 |0.2.8.8 | jjzwpy(a)yahoo.com | 8z4w2t6qteADFfb6 | 1 > 1 | 0 |12:45:39| 64.137.197.233 | ca | 9001 | 9030 |0.2.8.8 | malvina.maybury(a)gmail.com | CHWMSRVU | 1 > 1 | 0 |13:20:17| 64.137.189.77 | ca | 9001 | 9030 |0.2.8.8 | pwcrack(a)pwcrack.com | CACpwcrackgnt4 | 1 > Fingerprints: > FCAA8608123018476C576AE44AFBC2367D3333AB,653BDEEB516FD16917A45A2DD44272F59C765EF5,82B6083CA4FCC777320CE03EA45BB9380A45A4E7,9D0CBF2C789B9C88F1FE403DA3D5B849B182EAD4,56879AF8A29B1354ED751B26E2D4D3F3C44F2096,FA94C4060AD0BBE913676F090F6BA6706B97F205 > someone trying hard to look different? :)

1 0

Re: [tor-relays] Squalala tor relays: please update 'MyFamily' in your torrc
by nusenu 06 Feb '17

06 Feb '17

Hi BPM Squalala, thanks for adding two more relays, please do not forget to update your MyFamily setting. thanks, nusenu https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… +---------------------+-------------+--------------+ | first_seen | nickname | eFamilyCount | +---------------------+-------------+--------------+ | 2016-09-18 12:00:00 | RedOctober | 3 | | 2016-09-29 16:00:00 | 5OfNovember | 3 | | 2016-12-07 22:00:00 | May68 | 3 | | 2017-02-02 16:00:00 | 9OfDecember | NULL | | 2017-02-03 19:00:00 | 14OfJuly | NULL | +---------------------+-------------+--------------+

1 0

Problem upgrading Tor to 0.2.9.9 on Raspbian (Debian Jessie)
by fr33d0m4all 03 Feb '17

03 Feb '17

Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie): # apt list --upgradable -a Listing... Done tor-geoipdb/stable 0.2.9.9-1~d80.jessie+1 all [upgradable from: 0.2.9.8-2~d80.jessie+1] tor-geoipdb/now 0.2.9.8-2~d80.jessie+1 all [installed,upgradable to: 0.2.9.9-1~d80.jessie+1] tor-geoipdb/stable 0.2.5.12-4 all tor-geoipdb package could be upgrade but the tor package on which it depends is not available: # apt install tor-geoipdb Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: tor-geoipdb : Depends: tor (>= 0.2.9.9-1~d80.jessie+1) but 0.2.9.8-2~d80.jessie+1 is to be installed E: Unable to correct problems, you have held broken packages. Thank you in advance for any answer, Fr33d0m4All -- _____________________________________________________________ PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4 IRC Nick: fr33d0m4all (OFTC & Freenode) _____________________________________________________________

4 4

Minimum port 80 and 443 exit policy
by Mass Tor 03 Feb '17

03 Feb '17

Hey all, I was wondering what the minimum exit policy was (wrt port 80 and 443) for a Tor exit relay. I cant find any documentation about the minimum exit policy. Is it possible to have an exit relay exit only to a /16 or a /8 on port 80 and 443? I've tried having an exit policy that allows exiting to just a /16 on port 80 and 443 and it seems to not stick. Best

4 3

blazingvpn tor relays: please specify 'MyFamily' in your torrc
by nusenu 01 Feb '17

01 Feb '17

Hi blazingvpn tor relay operator, thanks for adding 4 more tor relays to the network! Please do not forget to set the MyFamily parameter in your torrc configuration to tell clients your relays belong to a single operator. If you need help with the MyFamily option let us know. thanks, nusenu +------------+-----------------+----------------+ | first_seen | IP | eMyFamilyCount | +------------+-----------------+----------------+ | 2016-12-17 | 163.172.190.249 | NULL | | 2016-12-31 | 108.61.128.176 | NULL | | 2016-12-31 | 51.15.47.106 | NULL | | 2016-12-31 | 51.15.58.152 | NULL | | 2017-01-06 | 185.163.45.249 | NULL | +------------+-----------------+----------------+

6 19

The Onion Box v3.2: Web Interface for your Tor relay
by theonionbox＠gmx.com 31 Jan '17

31 Jan '17

6 8

[OT] VPNGate needs nodes
by grarpamp 31 Jan '17

31 Jan '17

For those of you offering more than one service on your box, an example among many other circumvention / overlay networks you might like to support... http://www.vpngate.net/

2 1

Run a bridge or relay?
by Sebastian Hoffmann 29 Jan '17

29 Jan '17

Hi all, I've been running a relay for several months now. In the last weeks I read a bit about the censorship in turkey and asked myself how to help if normal Tor services are blocked. Obfs4 could help. But on the pages from torproject about running a relay you are told to run a relay if you can and a bridge only under certain circumstances. But... are there enough bridges? If I were the turkey administration, I would try to block all the bridges I could find one by one. So... do we really have enough bridges out there?

3 2

Updates removes status flags
by a tor op 29 Jan '17

29 Jan '17

Hi When a tor admin updates a tor node, what is the reasoning for punishing the status by removing flags like the guard flag? The node may have been up for months on end without issues and goes down for a few minutes during install and restart and comes up with a newer version, hence it is clearly updated. And the guard flag goes away. Doesn't seem really appropriate. Unless it's to indicate caution due to new version perhaps not being stable. But then that's what you do pre-prod testing in-house for. A TOR bridge op

3 3

ae rises and rises
by Felix 29 Jan '17

29 Jan '17

Please check out https:// metrics.torproject.org/userstats-relay-country.html?start=2015-10-22&end=20… vs https:// metrics.torproject.org/userstats-relay-country.html?start=2015-10-22&end=20… -- I this cool or not?

3 3

Atlas: Short term bandwidth charts missing ?
by mistral.relay＠posteo.net 28 Jan '17

28 Jan '17

Maybe it's just me - but I tried three different browsers and usually can't see the short term usage charts on Atlas, i.e. 3-days and 1 week bandwidth charts are usually just blank. Two random examples where I can't see the charts (but there is data; monthly and yearly charts showing up quite well): https://atlas.torproject.org/#details/F3F8B1A79C6781609B443CF0C1A130C85EB60… https://atlas.torproject.org/#details/7D278652898C38878F51D93969EB88C497BFB… Sorry, if this is my local issue but I just can't find the reason for it...

4 6

Please enable IPv6 on your relay!
by Moritz Bartl 28 Jan '17

28 Jan '17

Hi! We still have a depressingly low number of relays that support IPv6 (currently only ~120 of ~1900 relays). If your host supports IPv6, please enable it, especially if you run an exit! This has to be done explicitly. https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto In short, you add: ORPort [IPv6::address]:port IPv6Exit 1 ExitPolicy reject6 *:* (or a more open exit policy respectively) Thanks! -- Moritz Bartl https://www.torservers.net/

30 42

Fwd: netbackup.gs tor relays: please specify 'MyFamily' in your torrc
by netbackup.gs 28 Jan '17

28 Jan '17

3 5

Which is best for Tor: libevent v.2.0.22 or v2.1.8?
by Steve Snyder 26 Jan '17

26 Jan '17

With the long-awaited v2.1.8 of LibEvent recently released, this brings up the question: which is more suitable for use with contemporary versions of Tor, the older v2.0.22-stable or the shiny-new v2.1.8-stable? Thanks.

1 0

Fwd: US-CERT Avalanche Notification INC000010
by Monkey Pet 24 Jan '17

24 Jan '17

I received the following email from my ISP, the IP belongs to the tor exit node. I am wondering if the DHS is sending it out to all tor exit nodes? We received a notice from Homeland Security that a device using your current IP address is infected the Avalanche Malware. The full details are below. Please run antivirus and network security software on all your devices immediately. Thank you, ISP A trusted third party notified the Department of Homeland Security United States National Cybersecurity & Communications Integration Center (NCCIC) that one or more machines on your network was infected with malware associated with the Avalanche botnet infrastructure during December 2016. Avalanche is a large global network hosting infrastructure used by cyber criminals to conduct phishing and malware distribution campaigns and money mule schemes. A system infected with Avalanche associated malware may be subject to malicious activity including the theft of user credentials and other sensitive data, such as banking and credit card information. Some of the malware has the capability to encrypt user files and demand a ransom be paid by the victim to regain access to those files. In addition, the malware may allow criminals unauthorized remote access to the infected computer. Infected systems could be used to conduct distributed denial-of-service (DDoS) attacks. For additional information, please see the following US-CERT Technical Alert (TA16-336A): https://www.us-cert.gov/ncas/alerts/TA16-336A

2 1

Network is unreachable?
by niftybunny 24 Jan '17

24 Jan '17

xxx@xxxx:~# wget https://www.torproject.org/dist/tor-0.2.9.9.tar.gz converted 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (ANSI_X3.4-1968) -> 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (UTF-8) --2017-01-23 22:12:32-- https://www.torproject.org/dist/tor-0.2.9.9.tar.gz Resolving www.torproject.org (www.torproject.org) 2620:0:6b0:b:1a1a:0:26e5:4810, 2001:858:2:2:aabb:0:563b:1e28, 2001:41b8:202:deb:213:21ff:fe20:1426, ... Connecting to www.torproject.org (www.torproject.org)|2620:0:6b0:b:1a1a:0:26e5:4810|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2001:858:2:2:aabb:0:563b:1e28|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2a01:4f8:172:1b46:0:abba:5:1|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|82.195.75.101|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://dist.torproject.org/tor-0.2.9.9.tar.gz [following] converted 'https://dist.torproject.org/tor-0.2.9.9.tar.gz' (ANSI_X3.4-1968) -> 'https://dist.torproject.org/tor-0.2.9.9.tar.gz' (UTF-8) --2017-01-23 22:12:36-- https://dist.torproject.org/tor-0.2.9.9.tar.gz Resolving dist.torproject.org (dist.torproject.org) 2620:0:6b0:b:1a1a:0:26e5:4810, 2001:41b8:202:deb:213:21ff:fe20:1426, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2620:0:6b0:b:1a1a:0:26e5:4810|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|2a01:4f8:172:1b46:0:abba:5:1|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|2a01:4f8:211:6e8:0:823:2:1|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|38.229.72.16|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 5534005 (5.3M) [application/x-gzip] Saving to: 'tor-0.2.9.9.tar.gz' tor-0.2.9.9.tar.gz 100%[===================================================================================================================>] 5.28M 9.89MB/s in 0.5s 2017-01-23 22:12:41 (9.89 MB/s) - 'tor-0.2.9.9.tar.gz' saved [5534005/5534005] Is this normal behaviour? niftybunny abuse(a)to-surf-and-protect.net

4 12

Re: [tor-relays] 'MyFamily' .... torworld.org
by Paul 20 Jan '17

20 Jan '17

Hey, why don’t you just explain to the relay mailing list what it is all about..? Why are you different to "abuse [AT] torworld.org " and where are you probably the same ? What is your idea (business model) behind , why are supporting Tor in such a heavy way ? What are your driving forces...? Its not a must, but it would be less suspicious for somebody with you size! Thanks and Regards - to whom ever - Paul Am 19.01.2017 um 05:22 schrieb e: > Thanks for the heads up Paul.

3 3

Middle relay still an useful contribution?
by Ortez 20 Jan '17

20 Jan '17

Hello tor relay operators, I'm thinking about creating another tor middle relay, but i'm not sure if this is still a good contribution to the tor network. When i'm looking at some of the relay stats out there, there are so many middle relays, which getting almost no traffic. If i purchase a server, i want to make sure the money i will spend every month will make a difference. I know, an exit node may be the better option and those will get a lot of traffic, but i'm not very happy with the consequences which i may face. It's also very difficult to find a provider, which is cool with an exit node. Whats your opinion?

7 7

Proton now takes Tor
by Gumby 19 Jan '17

19 Jan '17

Nice to finally see this... "The encrypted email provider announced Thursday it will allow its users to access the site through the Tor anonymity service. The aim is to allow its more than 2 million users access the provider by taking "active measures to defend against state-sponsored censorship," such as government-mandated blocks at the internet provider level. Users of the Tor Browser can now access the site at https://protonirockerxow.onion. "

1 0

SIGHUP causing obfs warning/disabling
by Geoff Down 19 Jan '17

19 Jan '17

Hi, I sent a SIGHUP to the tor process after altering the torrc and got this effect: Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file. Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method error. (obfs3 Could not set up listener (0.0.0.0:xxxxx) for 'obfs3' (Address already in use).) Jan 19 00:47:55.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed. It did it again when I restored the torrc and SIGHUPed again. Obfs3 is still running and listening afaict: tor 17356 0.0 0.2 49944 1736 ?? S 20Dec16 0:13.04 /opt/local/Library/Frameworks/Python.... Python 17356 tor 3u IPv4 0x02eb32a4 0t0 TCP *:xxxxx (LISTEN) Bug or !Bug ? GD -- http://www.fastmail.com - mmm... Fastmail...

3 6