[tor-bugs] #16769 [Tor]: add two new functions when manually calling --keygen for better management

[Tor Bug Tracker & Wiki]

#16769: add two new functions when manually calling --keygen for better management
-------------------------+-------------------------------------------------
     Reporter:  s7r      |      Owner:  nickm
         Type:  defect   |     Status:  needs_revision
     Priority:  normal   |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor      |    Version:  Tor: 0.2.7.2-alpha
   Resolution:           |   Keywords:  ed25519, relay, keys,
Actual Points:           |  TorCoreTeam201509, PostFreeze027
       Points:           |  Parent ID:  #16645
-------------------------+-------------------------------------------------
Changes (by dgoulet):

 * status:  needs_review => needs_revision


Comment:

 It's weirdly working for me and I'm not 100% sure if it's the intended
 behavior. Here is my scenario:

 {{{
 keys/$ ls
 .  ..
 keys/$ tor --keygen --master-key mykey
 [...]
 keys/$ ls
 .  ..  ed25519_signing_cert  ed25519_signing_secret_key  mykey
 mykey_public_key
 keys/$
 }}}

 So good so far but then changing the password of `mykey` is not possible
 though. Maybe it's "upcoming feature", not sure. It was reported in the
 last s7r's comment but unclear if it was suppose to be fixed since tor is
 clearly trying to read "mykey".

 {{{
 keys/$ tor --newpass --keygen --master-key mykey
 [...]
 [warn] Unable to read mykey: Invalid argument
 }}}

 Second thing, if I use the default use case, `tor --keygen`, I get keys
 and a signing cert with its key. Then, right away, if I change the
 password with `tor --keygen --newpass`, I get a brand new signing
 cert/key. Again reported in s7r comment but comment:8 seems to indicate
 it's fixed?

 Note also that those two new options without a manpage entry will not be
 very useful.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16769#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online