[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #16790 [Tor]: Tor should reload keys from disk when receiving a SIGHUP

#16790: Tor should reload keys from disk when receiving a SIGHUP
-------------------------+-------------------------------------------------
     Reporter:  s7r      |      Owner:  nickm
         Type:  defect   |     Status:  needs_review
     Priority:  normal   |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor      |    Version:  Tor: 0.2.7.2-alpha
   Resolution:           |   Keywords:  TorCoreTeam201508, ed25519,
Actual Points:           |  identity keys
       Points:           |  Parent ID:
-------------------------+-------------------------------------------------

Comment (by nickm):

 Replying to [comment:3 s7r]:
 > Just to make sure: the option is enforced only when Tor '''wants''' or
 '''needs''' to generate new signing key and certificate (like when the
 signing key and certificate it has loaded in memory are going to expire
 soon), and is ignored otherwise?
 >
 > I have deleted ed25519_master_id_public_key and only left a valid
 certificate and signing key, and sent a HUP signal to Tor, it reloaded
 just fine but did not generate and write to disk
 ed25519_master_id_public_key from the certificate, as we normally do when
 we start.
 >
 > This has no importance - the behavior is correct either way just want to
 make sure I am describing it correctly in the documentation.

 Hmm. I'm not 100% sure I understand the question here.  :/

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16790#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs