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

[tor-bugs] #25120 [Core Tor/Tor]: getrandom() syscall failure warning should be a notice and worded better



#25120: getrandom() syscall failure warning should be a notice and worded better
------------------------------+--------------------------------
     Reporter:  catalyst      |      Owner:  (none)
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:  Tor: 0.3.3.x-final
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+--------------------------------
 The logging improvement for error handling of the `getrandom()` syscall in
 #24500 could be further improved:

 * The log level should possibly be NOTICE rather than WARN.
 * The log message should mention that tor will fall back to alternative
 sources of randomness.
 * Maybe we want to mention header/kernel version mismatches as a specific
 common reason for this issue.

 Yes, some of the fallbacks are somewhat dangerous, like `/dev/urandom`
 might not be seeded yet. etc,.

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