check Tor for local clock leaks

Various local clock leaks have been identified in past.

• #4852 (moved)
• #7277 (closed)
• #8751 (moved)
• #16659 (moved)

Please think through, and perhaps grep the code, if there are any others. If there are none, this ticket can be closed.

changed milestone to %Tor: unspecified

added analysis component::core tor/tor milestone::Tor: unspecified points::3 priority::medium severity::normal status::new term-project? tor-client type::task labels

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:
Reviewer: N/A to N/A
Points: N/A to medium

Trac:
Points: medium to 3

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???
Keywords: N/A deleted, isaremoved added

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:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

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

Trac:
Keywords: isaremoved deleted, N/A added

Trac:
Keywords: N/A deleted, analysis tor-client term-project? added

changed time estimate to 24h

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