Extend TLS RSA link keys to 2048-bit

When we implement proposal 220 , we'll need to have stronger per-connection TLS link keys, or else the link key will be the weak point.

In #6088 (moved), we investigated this; I made a branch called "ticket6088_hax" to try out the right fix.

changed milestone to %Tor: 0.2.9.x-final

added 027-triaged-1-in 028-triaged TorCoreTeam201608 actualpoints::0 component::core tor/tor milestone::Tor: 0.2.9.x-final owner::nickm parent::15055 points::.1 priority::high prop-220 resolution::implemented severity::normal sponsor::U-must status::closed tor-relay type::enhancement version::tor 0.2.7 labels

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

Trac:
Parent: #12498 (moved) to #15054 (moved)

Hm. We can do something much simpler than the ticket6088_hax approach if we do this after we remove more support for pre-v3 handshakes.

(Assuming we can remove support for pre-v3 handshakes.)

Trac:
Status: new to assigned

Marking more tickets as triaged-in for 0.2.7

Trac:
Keywords: tor-relay prop-220 deleted, prop-220, tor-relay, 027-triaged-1-in added

Trac:
Priority: normal to major
Points: N/A to small
Keywords: N/A deleted, SponsorU added
Version: N/A to Tor: 0.2.7

My "ticket6088_hax_v2" branch is now rebased.

Trac:
Keywords: N/A deleted, TorCoreTeam201507 added

Trac:
Keywords: TorCoreTeam201507 deleted, TorCoreTeam201508 added

Trac:
Owner: N/A to nickm

Trac:
Keywords: TorCoreTeam201508 deleted, TorCoreTeam201509 added
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

Trac:
Keywords: N/A deleted, 028-triaged added

Bulk-replace SponsorU keyword with SponsorU field.

Trac:
Sponsor: N/A to SponsorU
Keywords: SponsorU deleted, N/A added

It is impossible that we will fix all 252 currently open 028 tickets before 028 releases. Time to move some out. This is my first pass through the "assigned" tickets with no owner, looking for things to move to ???.

If somebody thinks they can get these done before the 0.2.8 timeout, please assign it to yourself and move it back?

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

Trac:
Sponsor: SponsorU to SponsorU-must

Removing TorCoreTeam201509 from these tickets, since we do not own a time machine.

Trac:
Keywords: TorCoreTeam201509 deleted, N/A added

Is this only for the edge case where we don't use the stronger ECC link crypto?

Seems like we should focus on getting everybody on to the better crypto, rather than doing this ticket.

Trac:
Reviewer: N/A to N/A
Severity: N/A to Blocker

(trac fail)

Trac:
Severity: Blocker to Normal