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