[tor-dev] protecting users from known relay groups with end-to-end correlation capabilities

[nusenu]

>> Examples (generated daily):
>> https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dangerous_relaygroups.txt
>> (see CC)
> 
> This is a useful check, but it is insufficient.
> Can you please produce a similar list for middles and exits by the same
> operator?

done
https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dangerous_relaygroups.txt


>> 1) try to contact the operators and give them time to fix it
>> I've done that multiple times but haven't been successful [1]
> 
> Have you tried emailing them individually?
> I've typically got better results that way.

Yes I did.
Just one example:
https://lists.torproject.org/pipermail/tor-relays/2016-November/010950.html


>> 2) build tools to easily/automatically manage MyFamily
>> done[2], but it is unlikely to be used
> 
> Maybe one solution is to build a generic tool that works with more than
> just ansible?

other example by coldhakca
https://github.com/coldhakca/sync_family




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20161202/54606776/attachment.sig>