fsync ed25519 master key files before closing them.

Weasel says this is a good idea, and IMO it can't hurt.

changed milestone to %Tor: unspecified

added component::core tor/tor easy ed25519 fsync milestone::Tor: unspecified points::.2 priority::very low severity::normal status::new tor-relay type::defect labels

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

Trac:
Keywords: N/A deleted, sponsorU, ed25519, TorCoreTeam201508 added
Owner: N/A to nickm
Status: new to accepted

Do we want to do the RSA keys while we're at it? We don't seem to be doing fsync at all in the current code, unless it's spelt differently.

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

Bulk-replace SponsorU keyword with SponsorU field.

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

Marking as trivial because if we crash before successfully saving the key, it's fine because we just generate a new one the next time.

Trac:
Keywords: sponsorU deleted, N/A added
Priority: normal to trivial

Trac:
Sponsor: SponsorU to SponsorU-can

Trac:
Severity: N/A to Normal
Sponsor: SponsorU-can to N/A
Reviewer: N/A to N/A
Points: N/A to .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: ed25519 deleted, ed25519 tor-relay fsync easy added

These tickets are not things I'm currently working on. They may be important, but they don't need to be done by me specifically. Un-assigning.

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

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

Trac:
Status: assigned to new

changed time estimate to 1h 36m

moved to tpo/core/tor#16598