Fix and re-enable --master-key option, possibly --out (for keys) and possibly --nopass for non-interactive key generation

See #16769 (moved) -- it proposed a few command-line arguments to make ed25519 key management easier. I got one of them implemented, but the rest weren't ready for 0.2.7.

changed milestone to %Tor: unspecified

added cli component::core tor/tor key-management milestone::Tor: unspecified points::small/medium priority::medium severity::normal status::new tor-relay type::enhancement usability labels

Trac:
Cc: N/A to s7r

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

Trac:
Sponsor: N/A to SponsorU

Trac:
Points: N/A to small/medium

Trac:
Username: tyseom
Cc: s7r to s7r, tyseom
Severity: N/A to Normal

We have been asked on the mail list for an option to create ed25519 master id keys on demand with --keygen in a non-interactive way for management scripts or applications which interact with Tor. Currently, when calling --keygen we are asked for a passphrase (it's not mandatory, we can press enter and proceed with an unencrypted master id key but it cannot be done in a non-interactive way).

nusenu suggested and me and teor think it's a good idea to also have a --nopass option to use with --keygen. When used Tor will just create an unencrypted master id key without asking for further input.

Trac:
Summary: Fix and re-enable --master-key option and possibly --out (for keys) to Fix and re-enable --master-key option, possibly --out (for keys) and possibly --nopass for non-interactive key generation

Since --master-key and --out are meant to split in 2 the attributes of --DataDirectory and eliminate the requirement of of a "keys" subfolder, we should code it in a way that these cannot be used together, to avoid confusions.

--DataDirectory will expect to find the master identity key in the given path under a "keys" subfolder under the filename "ed25519_master_id_secret_key" or "ed25519_master_id_secret_key_encrypted" and save all the output files in the same place.

--master-key and --out will require a direct path to the master identity key that can have any filename and a direct path for saving the output files. Might as well treat --master-key and --out dependent on each other.

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

These tickets, though owned by me, are not deliverables I can realistically deliver by the 0.2.8 freeze window.

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

Trac:
Sponsor: SponsorU to SponsorU-can

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

tickets market to be removed from milestone 029

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

Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.

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

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Trac:
Status: assigned to new

Trac:
Keywords: SponsorU-deferred deleted, tor-relay key-management usability cli added
Reviewer: N/A to N/A

mentioned in issue #17603 (moved)

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