valid MyFamily syntax variations ('$FP=nick' ?)
-----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 combination: $fp=nick Are they actually valid or is this a bug or can one actually specify arbitrary strings there? (dir auths and onionoo apparently accept them) thanks [1] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n504 [2] https://atlas.torproject.org/#details/2B76359D3AAA94CA107F447D2D14E481A99EB2... (search for KosakaKirino) [3] https://collector.torproject.org/recent/relay-descriptors/server-descriptors... (this url has a lifetime) -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVa2WkAAoJEFv7XvVCELh0jEwQAJqdeZaFpRWPfI9/17o7aEKI Jx8Lp811GGwr4STO41ixwOIQ69hjNuav47apcmR4AsUVAq8zkSnzljKyYtVnp7qH 4EHx0kqIop92s9de1AFKg2XDnZ3u4eSN6z53VXeO2+/jFl2CgMVarzLYPHNBBF/x ev3zMk8gYsGA7K5TowZ+HnMalXhHLpTvO+iPPzNF6eY3/pG31hImFfHvhkJ5nrzB gex9wmCTXigM6I1mcT8mK8OH/2+MkNFra2h4tcEmqzmzRdWx1UWDTgl97Jp2injL UxuHL1RkoGLqlZ/MDiMiZPa4JurNRKgBXdZNsASOvcX8ZiPiCzqbbCm4hN4Rsidi ROWR8AcadA/9a5Ovi0z8IhxUiF8Ks2Wadeovp4w+E2NuYvFNmUpvkH0jVSViSE8n v+XClj0DX8oHirRqp80M0o5GpOB2hsRzT0+QhRFKYbikW2CRziM1ECWknw3aj3/z VPohoo6bkkLLBfrrXdgqclvgtoG/zPl8Ef203pmyTjPCFEdx4mJTLzq+hmjoaPsI h+RweF+HvDc0qM+6fiYeHExQl7YMNuT6GbG58lK6V8c+r++FIrPwfyOepAddoE0p dTAHfqYMYhDL952z916tmNNPnHXsUu8hVaIVuB9RvYjAU9FpPAz5Q5CDaIu+F4TY kb9dxHK1c8IHOGamYMOD =tbZE -----END PGP SIGNATURE-----
-----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 work back when we were using Named / Unnamed flags. If the relay had the Named flag, you could just enter its nickname at Tor would automatically map that nickname to its proper fingerprint. It did not work for relays with Unnamed flag or relays without both Named and Unnamed flags. I have opened a ticket for this on trac, but we fixed the FAQ. https://trac.torproject.org/projects/tor/ticket/12092 On 5/31/2015 10:48 PM, nusenu wrote:
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 combination: $fp=nick
Are they actually valid or is this a bug or can one actually specify arbitrary strings there? (dir auths and onionoo apparently accept them)
thanks
[1] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n504
[2] https://atlas.torproject.org/#details/2B76359D3AAA94CA107F447D2D14E481 A99EB207
(search for KosakaKirino) [3] https://collector.torproject.org/recent/relay-descriptors/server-descr iptors/2015-05-30-14-05-48-server-descriptors
(this url has a lifetime)
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBCAAGBQJVa2o+AAoJEIN/pSyBJlsR6qgH/jOO//s8CGKkrGYRxWMHrSWK JUhH4xj8YPm7fTiDDH2MmKerGbC3N1l2ENKs03f1zDWfzxuxuWch2kdA+mN7GUaB xPAeAyksk4Rp6eMs9DhnZLUTLC1vHbta7Yx9qlVs5sc5aeR+HbKMl7jfIHStGQxF swhY2Er4bvMj4VbtMnWbcqTP1037UyEIriTgdLxXgeb1B58BW/i3sjtqDpWuZSrc 7a1SCYOGfIzu96WJi542LGVft2VJmlwFlZwV8Nq3ph2cq6AhBfxVuTKauoUcdG43 JbdWmiYzTd9UpoIoc8X6Z9SJIz6FXMKKWIBN/xvNCJpueveDw9sz9IaFEtdvooo= =JQWJ -----END PGP SIGNATURE-----
-----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 email: "$2B76359D3AAA94CA107F447D2D14E481A99EB207=Konata","$827BF0F1E52B82D69B3CE3DFEE1F1FE3A11042FD=KosakaKirino" (onionoo excerpt) have a look at this relay's family: https://atlas.torproject.org/#details/2B76359D3AAA94CA107F447D2D14E481 A99EB207 Normally you see, fingerprints only: $FP1, $FP2, ... or Nicknames only: "PPTOR0042","PPTOR0043","PPTOR0044", ... or nicknames next to fingerprints: $FP1, oilsrv1, ... -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVa23KAAoJEFv7XvVCELh02vQP/R/d0kNfQM3r30CZj4jXExbT XIuas66C/tqxtF8BPSQ3+xCUSStknbCEuhoMnjDJr4J5G5M5RaFk7XSOl4DbZ56/ GoVVKvG6HYEUHdnkAwk7dUDJQELZ+4UB4s24wPV/mFkzjx/503dA7TWeVWE9O2/E rnUvPPo8rMZ8vh6rksgBId3XvqFl6ShHduToNe83leomwl1V9qZY5F28dUrBkcFp ZIPhPsnonZYXRqlsW6WJlFWwAfTou5do8H7yJSAZd6+0+w0PLZKoF0pzH7vE5Ht8 T9dKQSw/9ZFbL8iJMdf0lVWpkhDGKHkDEOx7X8oRAVBrKdYj7xvnGhcj8XkwLGp3 h0L3pTqH3ApqlohCyuSA3ePYw4Cwy1ZJt0ix0t8PDRmm+j/r2uxELZHyWF7tV8CS LCpKLnWIecEOtA9fnn4eCTLqQQ/PZgSqJ3pJdhK8wFQXSHOD0vr0xjssPDohIfE3 xtBSQocainlCLtaWc4ickrDpZgldIVSuKaSRxGs67Pxd4qxxaQEDPG3F+UrCbUJU Xoy2bD9LXhD56H8mKp35L0wOBK/rl81HHlVztNqUVvNN/kyHvFFb1KRhtQaXKTYg NLefBY9/a+P3cHZ/Yv6PlugyNWQmc5QiqrLn3er11SOWde6Rg3si2jEEAz9MYiAT A8J3fn94VkaYR1f4uIlz =1VTB -----END PGP SIGNATURE-----
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. Metrics-lib parses this out in ServerDescriptorImpl [2]. Which then shows up in Atlas via Onionoo in DetailsStatus [3] during NodeDetailsStatusUpdater [4]. I hope that clears things up. (I know I skipped a full stack trace but its C and Java--cut me some slack) --leeroy [0] https://gitweb.torproject.org/tor.git/tree/src/or/nodelist.c#n499 [1] https://collector.torproject.org/recent/relay-descriptors/server-descriptors... [2] https://gitweb.torproject.org/metrics-lib.git/tree/src/org/torproject/descri... [3] https://gitweb.torproject.org/onionoo.git/tree/src/main/java/org/torproject/... [4] https://gitweb.torproject.org/onionoo.git/tree/src/main/java/org/torproject/...
participants (3)
-
l.m -
nusenu -
s7r