Opened 8 years ago

Last modified 2 years ago

#3021 assigned defect

Make the microdesc format a little more flexible, with optional TAP key

Reported by: nickm Owned by: nickm
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client prop245 tap-out format migration
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now we say that a microdesc starts with an onion-key field, and the onion-key contains a 1024-bit RSA key. This is true of any microdesc that we can currently _use_, but for caching purposes, we should probably be more tolerant so that we can have caches tolerate other key types in the distant happy future.

Child Tickets

Change History (20)

comment:1 Changed 8 years ago by nickm

Owner: set to nickm
Status: newassigned

comment:2 Changed 8 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.3.1-alpha

comment:3 Changed 8 years ago by nickm

Milestone: Tor: 0.2.3.1-alphaTor: 0.2.3.x-final

On consideration, giving this one back to 0.2.3.x-final. It's okay to make caches and clients more tolerant once they start fetching anything other than the basic microdesc flavor... and changing the content of the onion-key will want a new flavor anyway.

comment:4 Changed 8 years ago by nickm

Parent ID: #1748

comment:5 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

comment:6 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.3.x-final

Actually, this *could* be doable in December, if I can come up with an obviously right and noninvasive way to do it.

comment:7 Changed 7 years ago by nickm

Keywords: needs-proposal added
Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

I will not finish this by friday, and it would require design.

comment:8 Changed 7 years ago by nickm

Keywords: tor-client added

comment:9 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:10 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: unspecified

comment:11 Changed 4 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.7.x-final

These go in Tor 0.2.7

comment:12 Changed 4 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:13 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:14 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:15 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:16 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

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-out removed

comment:20 Changed 2 years ago by nickm

Keywords: prop245 tap-out format migration added; needs-proposal removed
Severity: Normal
Summary: Make the microdesc format a little more flexibleMake the microdesc format a little more flexible, with optional TAP key

prop245 needs some revision, but it explains one way to do this.

Note: See TracTickets for help on using tickets.