tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9
by Nick Mathewson 12 Feb '17

12 Feb '17

Hi, awesome relay operators! About two weeks ago, we put out 0.2.9.9, to fix a significant problem in our build process that led to an easy remote crash attack: o Major bugfixes (security): - Downgrade the "-ftrapv" option from "always on" to "only on when --enable-expensive-hardening is provided." This hardening option, like others, can turn survivable bugs into crashes -- and having it on by default made a (relatively harmless) integer overflow bug into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on 0.2.9.1-alpha. If you are on some earlier version of 0.2.9.x, it would be really great if you could update your relay some time soon: I want to put out a fix for the underlying bug here, but I'm hesitant to do so while there are still 700 crashable relays on the network. Also if you are on 0.3.0.1-alpha, you should upgrade to 0.3.0.2-alpha or later, but there are only around 53 relays still on that version, so I'm freaking out less about that. best wishes and many thanks, -- Nick

14 22

Reaching out to webiron
by Andrew Deason 12 Feb '17

12 Feb '17

I run an exit node, and as such, I get abuse emails like this from time to time: <https://lists.torproject.org/pipermail/tor-relays/2015-October/007982.html> Mostly I ignore them, but since their automated report contains the sentence "Please feel free to send us your comments or responses.", every so often I send something to complain about their practices. To my surprise, apparently somebody does actually read these because today I got a reply. I'm not reproducing the entire response here without permission (they seem kinda touchy), but the person that replied did mention that they have some kind of rbl "in beta" regarding tor exits. They seemed to imply that doing so was quite a burden on them, though, which I don't really understand (IME blocking tor exits is easy; intentionally so). I'm trying to keep the conversation going, but I was wondering if anyone from the tor project has tried to reach out to them in some kind of official way? I'm just some random guy, so I don't know if it would be preferable for someone more knowledgeable, or with more access to tor infrastructure, to be conversing with them. (e.g. teor) I assume some people will say this isn't even worth the effort; it's not like it's hard to just ignore those reports. But it doesn't take much effort to just try to talk ot them, and it perhaps helps to give tor a reputation of cooperation and helpfulness. -- Andrew Deason adeason(a)dson.org

11 23

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays