[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 s7r):

 I was interested if the reload keys from disk on SIGHUP operation happens
 only when the current loaded signing key and certificate are due to expire
 soon (and Tor will not try to reload keys from disk when receiving a
 SIGHUP if the ones it has in memory are valid for for a reasonable time in
 future).

 I have tested the latest branch, after receiving notifications that the
 medium term signing key and certificate will expire soon and Tor should
 try to generate new ones, I have manually generated new valid signing key
 and certificate and moved them to $datadirectory/keys and sent a SIGUP to
 Tor - no more notifications in logs.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16790#comment:6>
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