[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] handling of MyFamily for an outdated relay




Toralf Förster:
> Looking at his :
> 
> 
> I do wonder how to deal with deleting all /var/lib/tor/data2/* files
> of a Tor relay and running a new one with the same config (but now
> different key/fingerprint). I added the new fingerprint to the
> config, which now has 3 entries (the middle is 1 outdated):
> 
> MyFamily
> 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA,6EABEBF38CE7E3DF672C4DB01383606FE3EB2215,D11D11877769B9E617537B4B46BFB92B443DE33D
>
>  Is this the right way ? I'm asking b/c I do see now "Alleged Family
> Members" here:
> 
> https://atlas.torproject.org/#details/D11D11877769B9E617537B4B46BFB92B443DE33D


MyFamily requires mutual configuration. So if you have 3 relays you have
to change 3 torrc files if one relay changes its key.


Your new relay (D11D) lists the old one (6EAB) that used to be at that
address. That is why it is "alleged" (not mutual).

The question is probably: Why are you including 6EAB if you replaced it?


--
https://mastodon.social/@nusenu
twitter: @nusenu_

Attachment: signature.asc
Description: OpenPGP digital signature

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