[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5565 [Tor Relay]: MyFamily should provide an alternate non-idhex subscription mechanism
#5565: MyFamily should provide an alternate non-idhex subscription mechanism
-------------------------+--------------------------------------------------
Reporter: mikeperry | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor Relay | Version:
Keywords: | Parent: #5563
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by rransom):
Replying to [comment:8 mikeperry]:
> However, I think we should first try to find issues with a simple UUID-
based solution. Are there any?
A âsimple UUID-based solutionâ doesn't handle the case of a relay
administrable by two parties, each of whom also solely administers other
relays. (This has actually happened.)
> > If we do worry about that replay attack, things get messier; a relay's
operator will need to generate family-membership signatures once per
$INTERVAL per relay, and then upload them to the relay periodically. (In
this case, I wouldn't recommend putting the signature itself in the torrc;
reference a separate file instead.)
>
> Hrmm.. Yeah, already the complexity mounts. I forgot about re-using old
signatures and setting time limits/expiry. Thanks.
I'm not sure we should care about this replay attack; I just mentioned it
because someone had to.
The more important question is: Is MyFamily a good feature to keep?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5565#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs