- tor-relays - lists.torproject.org

(no subject)
by Даниил Орлов 07 Mar '17

07 Mar '17

1 0

(no subject)
by Raymond Bordt 07 Mar '17

07 Mar '17

1 0

new Atlas feature: Not Recommended Tor Version
by nusenu 07 Mar '17

07 Mar '17

I'd like to highlight a new Atlas feature [1]: Atlas now displays a red "!" if the relay runs a tor version that is not recommended by the tor directory authorities. Examples https://atlas.torproject.org/#/top10 Thanks to RaBe and irl for adding this. [1] https://trac.torproject.org/projects/tor/ticket/21367

5 5

torpids family seems outdated
by Felix 05 Mar '17

05 Mar '17

Hi torpids AT yahoo dot com Thank you very much for so many relays labeled torpids*. Are there contradictions in the announcement of the family ? Torstatus [1] returns 32 family members and fingerprints. Altas [2] shows as biggest family section a number of 8 relays. The manual compare of the fingerprints shows to me: * 8 relay fingerprints match and are within the pronounced family * the other 24 relays are out of the pronounced family Is the observation correct ? [1] http:// jlve2y45zacpbz6s.onion/router_detail.php?FP=0cf8f3e6590f45d50b70f2f7da6605eca6cd408f [2] https:// atlas.torproject.org/#details/6B7191639E179965FD694612C9B2C8FB4267B27D -- Best regards, Felix

1 0

www.artikel5ev.de relays: please update 'MyFamily' in your torrc
by nusenu 05 Mar '17

05 Mar '17

Hi artikel5ev, thanks for running tor relays. Please do not forget to set/update the MyFamily parameter in your torrc configuration to tell clients your relays belong to a single operator, otherwise they might use your relays in multiple positions within a circuit, which is rather bad for their anonymity. If you need help with the MyFamily option let us know. thanks, nusenu https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… https://github.com/nusenu/ansible-relayor The counter in the last column should match the number of rows: +---------------------+--------------+---------------+ | first_seen | nickname | FamilyMembers | +---------------------+--------------+---------------+ | 2014-04-11 23:00:00 | dc6jgk2 | 20 | | 2014-05-17 21:00:00 | dc6jgk3 | 20 | | 2014-06-09 18:00:00 | dc6jgk1 | 20 | | 2014-08-04 19:00:00 | dc6jgk4 | 20 | | 2016-07-22 22:00:00 | h3rmi | 19 | | 2016-09-05 17:00:00 | dc6jgk5 | 20 | | 2016-10-06 23:00:00 | dc6jgk6 | 20 | | 2016-10-19 19:00:00 | artikel5ev1 | 20 | | 2016-10-29 00:00:00 | artikel5ev2 | 20 | | 2016-11-04 03:00:00 | dc6jgk7 | 20 | | 2016-11-06 23:00:00 | dc6jgk8 | 20 | | 2016-11-07 19:00:00 | artikel5ev3 | 20 | | 2016-11-11 02:00:00 | dc6jgk9 | 20 | | 2016-11-11 02:00:00 | dc6jgk11 | 20 | | 2016-11-11 02:00:00 | dc6jgk10 | 20 | | 2016-11-13 04:00:00 | dc6jgk12 | 20 | | 2017-02-05 20:00:00 | tweinbrenner | 19 | | 2017-03-01 22:00:00 | utzer1 | 19 | | 2017-03-01 23:00:00 | utzer1 | NULL | | 2017-03-02 01:00:00 | utzer2 | 19 | | 2017-03-03 15:00:00 | tweinbrenner | NULL | | 2017-03-05 01:00:00 | Artikel5ev6 | 16 | +---------------------+--------------+---------------+ 22 rows

1 0

dipulse.it relays: please specify 'MyFamily' in your torrc
by nusenu 05 Mar '17

05 Mar '17

Hi, thanks for adding more tor relays. Please do not forget to set the MyFamily parameter in your torrc configuration to tell clients your relays belong to a single operator, otherwise they might use your relays in multiple positions within a circuit, which is rather bad for their anonymity. If you need help with the MyFamily option let us know. thanks, nusenu https://github.com/nusenu/ansible-relayor https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… ornetradar(a)riseup.net: > 2017-02-19 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | AS | CC | ORp | Dirp | OS | Version | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 | 12:53:10 | 163.172.189.100 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR15 | 1 > 1 | 0 | 12:49:39 | 163.172.181.240 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR16 | 1 > 1 | 0 | 12:45:42 | 163.172.187.152 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR14 | 1 > 1 | 0 | 12:51:17 | 163.172.183.161 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR18 | 1 > 1 | 0 | 12:42:14 | 163.172.160.239 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR13 | 1 > 1 | 0 | 12:52:08 | 163.172.183.220 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.2.8.12 | DipulseFR19 | 1 > 1 | 0 | 12:46:43 | 212.47.245.227 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR12 | 1 > 1 | 0 | 12:55:27 | 212.47.236.157 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR17 | 1 > 1 | 0 | 14:29:40 | 163.172.166.1 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR11 | 1 > Fingerprints: > 5928164F3759E3710393E7DC1ED69FACB669BE82,0211F6543B8EB8BE2AAD17ABD05635BD135FFCF7,D3FA077CE59A2D13B6E6B8C62B04A2C03BAC784F,8D60E9C8DB03BE39159B8824680ACCBD642ACF62,AF59C8E3CBB0B2C34D2BDCBA55CD7282BAA22B22,B66760160753DD26A6FD1B4B87F9CB3D0EEACC2D,619B69FD8F3A4642E2E8E40B5E97D2875496C829,B5CFDBA1E8DAFE061C5D259BBC44BF994ACB8C26,EFDCB52BD37CDDEFDD38DEF3F6C7A60DCCF099EE >

1 2

Relay not receiving Guard flag
by Norris Thomlinson 04 Mar '17

04 Mar '17

Hi all, I've had a relay running for 41 days, with Flags: Fast HSDir Running Stable V2Dir Valid...but no Guard flag. My impression from "Lifecycle of a new relay" at https://blog.torproject.org/blog/lifecycle-of-a-new-relay is that the Guard flag should be added within about 2 weeks of starting a relay. Is that post out of date? Or am I missing something I need to enable to allow my relay to be a Guard? Atlas entry for my relay: https://atlas.torproject.org/#details/9C2BF9B1E30EBB1A3836FA04BEEE8CC192CC1… Thanks! Norris Thomlinson Deep Green Resistance Webmaster

5 4

Re: [tor-relays] [OrNetRadar] AS: "EDIS GmbH" - Linux (15)
by nusenu 04 Mar '17

04 Mar '17

If you added 15 relays on 2017-02-24 (yesterday) on AS38478, please consider setting ContactInfo and MyFamily in your torrc (and maybe a more recent tor version). thanks ornetradar(a)riseup.net: > 2017-02-24 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | CC | ORp | Dirp |Version | ContactInfo | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 |15:31:23| 124.248.229.138 | hk | 9001 | 9051 |0.2.8.9 | None | coast | 1 > 1 | 0 |15:33:47| 124.248.229.140 | hk | 9001 | 9051 |0.2.8.9 | None | crop | 1 > 1 | 0 |15:35:17| 124.248.238.194 | hk | 9001 | 9051 |0.2.8.9 | None | beach | 1 > 1 | 0 |15:39:10| 124.248.238.197 | hk | 9001 | 9051 |0.2.8.9 | None | queen | 1 > 1 | 0 |15:51:44| 124.248.229.142 | hk | 9001 | 9051 |0.2.8.9 | None | castle | 1 > 1 | 0 |17:27:16| 103.44.66.2 | None | 9001 | 9051 |0.2.8.9 | None | tennis | 1 > 1 | 0 |17:39:25| 103.27.126.28 | hk | 9001 | 9051 |0.2.8.9 | None | court | 1 > 1 | 0 |17:48:57| 103.44.66.4 | None | 9001 | 9051 |0.2.8.9 | None | waterfall | 1 > 1 | 0 |17:58:26| 103.44.66.5 | None | 9001 | 9051 |0.2.8.9 | None | camp | 1 > 1 | 0 |18:06:15| 103.27.126.27 | hk | 9001 | 9051 |0.2.8.9 | None | fighter | 1 > 1 | 0 |18:25:53| 43.242.174.35 | hk | 9001 | 9051 |0.2.8.9 | None | burn | 1 > 1 | 0 |18:38:11| 43.242.174.36 | hk | 9001 | 9051 |0.2.8.9 | None | leisure | 1 > 1 | 0 |18:46:30| 43.242.174.37 | hk | 9001 | 9051 |0.2.8.9 | None | clerk | 1 > 1 | 0 |18:55:48| 150.107.44.3 | hk | 9001 | 9051 |0.2.8.9 | None | servant | 1 > 1 | 0 |19:00:45| 150.107.44.2 | hk | 9001 | 9051 |0.2.8.9 | None | mankind | 1 > Fingerprints: > 25214D40CD1747A06FA2E695E48AED0E988ABA61,25214D43D1FDAF97EBCB68C282D7AA247A1BC487,25214D43CF6621FD4FBEB6FC654A29702965094D,25214D42EC6083C31E1709D86CEBEFFCD4BE1958,7053866617EA5FD3AC0B5D4EB8CE6EC792F99AF5,AB559BE305A7A63962944D32A69AEB2AF9EAC7DC,AB559BE25926F720890BDAE88407E1A676883304,AB559BE2CA986C0EDEFBD78B48621DD36C349AD4,AB559BE02A323465AB8C3D0BB18EA04A1F13E32F,203281E1A349FAA241B6A66456A5AFD1C5B49410,203281E3EBC4E8AB7F040AD8A86B8767A5F6F849,203281E0784DE0DFB5C39C714BBBBA39E76AAA61,203281E37E44A5ABCEA7880DA47895197E92D546,203281E1226E3C1EEBA522409109C847AB14A2B9,203281E27627443DB6FE5E06250DDDB6D9718A0C >

5 14

Descriptor Published: never
by Jivan Amara 03 Mar '17

03 Mar '17

My relay, which was recently restarted has a value of 'never' for 'Descriptor Published'. Is this a problem & if so how would I remedy it? https://atlas.torproject.org/#details/880EA01C702B372843A309AAE71BCBE36213C…

2 2

Remove IP from list of known Tor exit nodes
by Paw 02 Mar '17

02 Mar '17

Dear all, By mistake I routed exit traffic from my Tor exit node through an IP that is used for NAT'ing where I live, for a short time. So now the NAT ip is found on https://check.torproject.org/exit-addresses which is a bit unfortunate, since cloudFlare now does CAPCHA check on my NAT traffic. Is there a way to remove my NAT ip from the list of Tor exit nodes? The NAT address does not see any Tor traffic anymore. Best regards, Paw

3 4