Move timeliness check out of tor_cert_checksig, or into tor_cert_get_checkable_sig

There's a mismatch in our certificate API: When we're doing single verification, we check the expiration time, but when we are doing batch verification, we rely on the caller to do so. We should make these functions do the same thing.

changed milestone to %Tor: 0.2.9.x-final

added 027-triaged-1-in 028-triaged TorCoreTeam201608 component::core tor/tor milestone::Tor: 0.2.9.x-final owner::nickm parent::15054 points::1 priority::medium resolution::implemented severity::normal sponsor::U-can status::closed tor-ed25519-proto type::defect version::tor 0.2.7 labels

Trac:
Status: new to assigned

Marking more tickets as triaged-in for 0.2.7

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

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

Trac:
Owner: N/A to nickm

Moving these tickets into 0.2.8. Not expecting to take patches for any into 0.2.7 at this late date. As usual, please say something if you disagree! :)

Trac:
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:
Keywords: SponsorU deleted, N/A added
Sponsor: N/A to SponsorU

Trac:
Priority: High to Medium

These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

Trac:
Sponsor: SponsorU to SponsorU-can

Trac:
Keywords: 028-triaged deleted, 028-triaged tor-ed25519-proto added
Reviewer: N/A to N/A
Severity: N/A to Normal

Trac:
Points: small to 1

Trac:
Keywords: 028-triaged tor-ed25519-proto deleted, 028-triaged tor-ed25519-proto TorCoreTeam201608 added

Done as part of my 15055_wip branch

Folding this back into #15055 (moved) , where it is implemented.

Trac:
Resolution: N/A to implemented
Status: assigned to closed

closed

changed time estimate to 8h

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