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

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.

changed milestone to %Tor: unspecified

added component::core tor/tor format migration milestone::Tor: unspecified priority::high prop245 severity::normal status::new tap-out tor-client type::defect labels

Trac:
Status: new to assigned
Owner: N/A to nickm

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.3.1-alpha

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.

Trac:
Milestone: Tor: 0.2.3.1-alpha to Tor: 0.2.3.x-final

Trac:
Parent: #1748 (moved) to N/A

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.4.x-final

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

Trac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.3.x-final

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

Trac:
Keywords: N/A deleted, needs-proposal added
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.4.x-final

Trac:
Keywords: needs-proposal deleted, needs-proposal tor-client added

Trac:
Component: Tor Client to Tor

Trac:
Milestone: Tor: 0.2.4.x-final to Tor: unspecified

These go in Tor 0.2.7

Trac:
Milestone: Tor: unspecified to Tor: 0.2.7.x-final

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

Trac:
Keywords: needs-proposal tor-client deleted, needs-proposal, 027-triaged-1-out, tor-client added

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

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

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

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, 027-triaged-in added

Trac:
Keywords: 027-triaged-in deleted, N/A added

Trac:
Keywords: 027-triaged-1-out deleted, N/A added

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

Trac:
Sponsor: N/A to N/A
Reviewer: N/A to N/A
Summary: Make the microdesc format a little more flexible to Make the microdesc format a little more flexible, with optional TAP key
Keywords: needs-proposal, tor-client deleted, tor-client prop245 tap-out format migration added
Severity: N/A to Normal

I am not actually working on these tickets, so they shouldn't be assigned to me.

Trac:
Owner: nickm to N/A

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

moved to tpo/core/tor#3021 (closed)