Re: [tor-relays] yui.cat relays: please update 'MyFamily' in your torrc

2017-02-25 Thread nusenu 

Hi Jordan,

thanks for running exit relays.

Please do not forget to 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_dangerous_relaygroups.txt

https://github.com/nusenu/ansible-relayor

+--++
| nickname | eFamilyMembers |
+--++
| yuicat1  |   NULL |
| yuicat2  |  4 |
| yuicat3  |   NULL |
| yuicat4  |  4 |
| yuicat5  |  4 |
| yuicat6  |  4 |
+--++



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] dipulse.it relays: please specify 'MyFamily' in your torrc

2017-02-25 Thread nusenu 
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_dangerous_relaygroups.txt

ornetra...@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
> 



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] CentOS Tor exit node broken after updating to 2.8.12

2017-02-25 Thread Chris 
Hello,

I recently upgraded my tor version to 2.8.12 from 2.8.9(?) I think.

Tor can now no longer bind to ports, as a regular user:

/[warn] Could not bind to 0.0.0.0:43: Permission denied/

As root:

/Feb 25 11:57:14.942 [notice] Opening OR listener on 0.0.0.0:43//
//Feb 25 11:57:14.942 [notice] Opening Directory listener on 0.0.0.0:9030//
//Feb 25 11:57:14.942 [notice] Closing partially-constructed Socks
listener on 127.0.0.1:9050//
//Feb 25 11:57:14.942 [notice] Closing partially-constructed Control
listener on 127.0.0.1:9051//
//Feb 25 11:57:14.942 [notice] Closing partially-constructed OR listener
on 0.0.0.0:43//
//Feb 25 11:57:14.942 [notice] Closing partially-constructed Directory
listener on 0.0.0.0:9030//
//Feb 25 11:57:14.942 [warn] Failed to parse/validate config: Failed to
bind one of the listener ports.//
/

In the former case, I tried using eip to allow tor to bind to ports
lower than 1024 but it made no difference.


I suspect this an issue with the configuration of the server rather than
tor. Where should I start?


Best,

Chris

-- 
Protect your privacy: encrypt your communications
GPG: CF7F98B2

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Is there a logical limit of MyFamily members?

2017-02-25 Thread John Ricketts 
Thank you.  :-)

> On Feb 25, 2017, at 03:01, nusenu  wrote:
> 
> 
> 
> John Ricketts:
>> I have 30 nodes now and my year end I intend to run enough to reach
>> 6% of exit probability.  I want to know if there is a logical limit
>> per family.
> 
> There is a max. descriptor size limit (20k) [1] and MyFamily is uploaded
> via descriptors.
> 
> Taking the descriptor of QuintexAirVPN26 as a sample you could probably
> fit another ~380 family members into that descriptor before you hit the
> descriptor limit (but any other changes like exit policy influence your
> descriptor size as well).
> 
> 
> [1] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n364
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Is there a logical limit of MyFamily members?

2017-02-25 Thread nusenu 


John Ricketts:
> I have 30 nodes now and my year end I intend to run enough to reach
> 6% of exit probability.  I want to know if there is a logical limit
> per family.

There is a max. descriptor size limit (20k) [1] and MyFamily is uploaded
via descriptors.

Taking the descriptor of QuintexAirVPN26 as a sample you could probably
fit another ~380 family members into that descriptor before you hit the
descriptor limit (but any other changes like exit policy influence your
descriptor size as well).


[1] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n364



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Is there a logical limit of MyFamily members?

2017-02-25 Thread John Ricketts 
All,

I have 30 nodes now and my year end I intend to run enough to reach 6% of exit 
probability.  I want to know if there is a logical limit per family.

Thanks!
John
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] [OrNetRadar] AS: "EDIS GmbH" - Linux (15)

2017-02-25 Thread nusenu 
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

ornetra...@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,203281E0784DE0DFB5C39C714A39E76AAA61,203281E37E44A5ABCEA7880DA47895197E92D546,203281E1226E3C1EEBA522409109C847AB14A2B9,203281E27627443DB6FE5E06250DDDB6D9718A0C
> 



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays