[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12498 [Tor]: Implement ed25519 identity keys (prop 220)
#12498: Implement ed25519 identity keys (prop 220)
-----------------------+--------------------------------
Reporter: asn | Owner: nickm
Type: task | Status: assigned
Priority: major | Milestone: Tor: 0.2.7.x-final
Component: Tor | Version:
Resolution: | Keywords: 026-triaged-1
Actual Points: | Parent ID:
Points: |
-----------------------+--------------------------------
Comment (by nickm):
So, I should re-summarize status:
This is NOT a complete implementation of proposal 220.
This branch DOES contain a complete implementation of proposal 228, and an
initial implementation of proposal 220: the parts about managing ed25519
keys, advertising them, signing with them, pinning them, and voting on
them.
Still to implement in this ticket:
* Change handling of certificate validity times in descriptors so that a
descriptor is either valid or not.
* Make sure that we regenerate new signing keys as needed.
* Only try to load master key in init_ed_keys() when we're making a
signing key cert.
Still to implement in other tickets:
* Link handshake.
* Circuit extension handshake
* Support offline master identity keys.
* Support new link identifiers in EXTEND cells
* Write a proposal for eventually removing RSA1024 identities
* Write a proposal for deprecating TAP
* User interface for identifying nodes by ed25519 key
* Family support for ed25519 keys (or some other family thing)
* Other stuff in prop220
* Controller interface
* Bridge identity support with ed25519
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12498#comment:13>
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