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

Re: [tor-bugs] #14901 [Tor]: Segfault when calling SETCONF

#14901: Segfault when calling SETCONF
------------------------+-----------------
     Reporter:  atagar  |      Owner:
         Type:  defect  |     Status:  new
     Priority:  major   |  Milestone:
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------

Comment (by Sebastian):

 Yup, in the past cpu_init didn't do very much so this wasn't a problem,
 but now we have to think a second about whether we should just call it
 always, no matter if we're a relay or not, if maybe we should just call it
 frequently as it looks mostly idempotent with the possible exception of
 crypto_seed_weak_rng which I haven't looked at, or if we need to do a
 bigger refactoring. My intuition would be to just call this on startup
 independent of whether we're a relay or not.

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