[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17349 [Tor]: Create an ed25519 shared randomness key for dirauths
#17349: Create an ed25519 shared randomness key for dirauths
--------------------+------------------------------------
Reporter: asn | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.2.8.x-final
Component: Tor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #16943 | Points:
Sponsor: |
--------------------+------------------------------------
Comment (by s7r):
asn: dgoulet: the code should know how to handle situations where the SR
key changes during protocol run, even during the run of only one phase of
the protocol (commit phase or reveal phase).
Accept any SR key and even multiple different SR keys in the same phase
for the same directory authority if it is properly linked to the ed25519
master identity key (which we could include in the consensus).
Since an expiration date exists, we have a 100% probability that the
medium term signing key (and implicitly SR key) will expire during a
protocol run (either commit phase, either reveal phase - doesn't matter).
Directory authorities should be able to replace medium term signing key
and HUP/reload/restart Tor at anytime without affecting anything.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17349#comment:6>
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