[tor-dev] Damian's Status Report - May 2015

2015-05-31 Thread Damian Johnson
Squirrels! Five newborn squirrels are in our tree! And they... oh right, code. Talk about code, Damian, like a professional. ... awww, but damn they're cute. Stem Release 1.4.1

[tor-dev] Visualising similarities between relay descriptors

2015-05-31 Thread Philipp Winter
Visualising the similarity between two Tor relay descriptors helps with finding Sybil attacks. I added code to sybilhunter [0] that takes as input relay descriptors, determines all (n^2)/2 pairwise similarities, and outputs DOT code (part of Graphviz) that illustrates relay clusters and what

Re: [tor-dev] valid MyFamily syntax variations ('$FP=nick' ?)

2015-05-31 Thread s7r
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, That would be invalid. I know there are some families which do it. You are free to enter a nickname at MyFamily parameter in your torrc, but it won't actually work for clients. Tor will still start on relay side and go on with it. It used to

Re: [tor-dev] valid MyFamily syntax variations ('$FP=nick' ?)

2015-05-31 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, based on your answer and linked trac entry, I assume my point was not entirely clear. I was specifically wondering about a combination of *both* ($FP=nickname) something I haven't seen till now: Example as provided in the URLs of my last

[tor-dev] valid MyFamily syntax variations ('$FP=nick' ?)

2015-05-31 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, according to the spec [1] relay ops can choose between fingerprint (with and without $ prefix) and nicknames when constructing their MyFamily configs. The man page recommends fingerprints. Now I'm faced with [2][3] families that use a

Re: [tor-dev] valid MyFamily syntax variations ('$FP=nick' ?)

2015-05-31 Thread l.m
Hi nusenu, The spec isn't done :P Seriously though, no it's not a bug. If you check nodelist [0] you'll see that this type of hex-encoded nickname is normal for generating a descriptor. If you check CollecTor history for the node your mention [1] you'll see the result of building a descriptor.

Re: [tor-dev] Sanitizing bridge descriptors containing ed25519 fields

2015-05-31 Thread Nick Mathewson
On Sat, May 30, 2015 at 5:16 PM, Karsten Loesing kars...@torproject.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/05/15 16:44, Nick Mathewson wrote: On Fri, May 29, 2015 at 4:23 PM, Karsten Loesing kars...@torproject.org wrote: router euler [scrubbed] 8000 0 0

[tor-dev] Tor Browser IsolateSOCKSAuth behavior questions.

2015-05-31 Thread Yawning Angel
Hello, I've been working on a dumb hack that lets me do things like this: https://imgur.com/3mah244 (Yes, that's a single Tor Browser instance, separate windows used for illustrative purposes.) It's still very raw and doesn't do everything I want it to do, so I'm not really releasing the code