Opened 4 years ago

Last modified 5 weeks ago

#15059 assigned enhancement

Allow UI to identify servers by Ed25519 keys

Reported by: nickm Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: tor-client, prop220, tor-ed25519-proto, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: #15054 Points: 3
Reviewer: Sponsor:

Description

Everything that currently allows users to identify servers by fingerprint, such as various torrc options and the .exit syntax, should allow Ed25519 keys as well.

Child Tickets

TicketTypeStatusOwnerSummary
#23472enhancementnewAdd support for ed25519 authorities and bridges to chutney

Change History (28)

comment:1 Changed 4 years ago by nickm

Status: newassigned

comment:2 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:3 Changed 4 years ago by isabela

Keywords: SponsorU added
Points: medium
Version: Tor: 0.2.7

comment:4 Changed 4 years ago by nickm

Owner: set to nickm

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:6 Changed 4 years ago by nickm

Keywords: 028-triaged added

comment:7 Changed 4 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:8 Changed 3 years ago by nickm

Priority: MediumLow

comment:9 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

These tickets, though owned by me, are not deliverables I can realistically deliver by the 0.2.8 freeze window.

comment:10 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-can

comment:11 Changed 3 years ago by nickm

Keywords: tor-ed25519-proto added

comment:12 Changed 3 years ago by isabela

Points: medium3

comment:13 Changed 3 years ago by nickm

Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final
Severity: Normal

comment:14 Changed 3 years ago by dgoulet

Keywords: triage-out-030-201612 added
Milestone: Tor: 0.3.0.x-finalTor: 0.3.1.x-final

Triaged out on December 2016 from 030 to 031.

comment:15 Changed 2 years ago by nickm

Sponsor: SponsorU-can

Clear sponsorS and sponsorU from open tickets in 0.3.1

comment:16 Changed 2 years ago by nickm

Milestone: Tor: 0.3.1.x-finalTor: 0.3.2.x-final

comment:17 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:18 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:19 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:20 Changed 2 years ago by nickm

Keywords: 028-triaged removed

comment:21 Changed 2 years ago by nickm

Keywords: triage-out-030-201612 removed

comment:22 Changed 23 months ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:23 Changed 23 months ago by catalyst

Back end support in #22173.

comment:24 Changed 18 months ago by dgoulet

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

comment:25 Changed 16 months ago by nickm

Keywords: 034-triage-20180328 added

comment:26 Changed 16 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:27 Changed 16 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:28 Changed 5 weeks ago by nickm

Owner: nickm deleted

These tickets are not things I'm currently working on. They may be important, but they don't need to be done by me specifically. Un-assigning.

Note: See TracTickets for help on using tickets.