Take a look at this ticket: https://dev.openwrt.org/ticket/9631
  ----- Original Message ----- 
  From: Weedy 
  To: OpenWrt Development List 
  Sent: Friday, October 18, 2013 1:02 AM
  Subject: Re: [OpenWrt-Devel] Quick hack for kernel entropy problem on MIPS


  On 17 Oct 2013 13:07, "chrono" <chr...@open-resource.org> wrote:
  >>>>
  >>>> root@OpenWrt:/# cat /proc/sys/kernel/random/entropy_avail
  >>>> 0
  >>>
  >>> Uhhhhhh ok?
  >>> root@OpenWrt:~# cat /proc/sys/kernel/random/entropy_avail
  >>> 1189
  >>
  >>
  >> What's your uptime? Entropy is added to the pool e.g. based on network
  >> activity. The issue is that the pool is empty right after boot up.
  >
  >
  > Well it's not anymore (with the patch).
  > That may be due to the fact that network is the only source of entropy
  > left on MIPS, that is something I personally wouldn't accept as enough
  > anymore.
  >
  > As I reckon there has been a lengthy discussion about it already and
  > many people raised their concerns.
  >
  >                      
ecurity/meldung/Linux-auf-MIPS-jetzt-wieder-mit-mehr-Zufall-1963604.html
  >
  > (sorry for german link)
  >
  > That patch wouldn't work with 3.3.8 due to include dependencies I
  > wasn't willing to follow up.
  >
  > The attached patch will re-enable CPU interrupts as entropy source,
  > at least for AR71xx/mips32r3 and will do so right away, which might
  > also solve issues with hostapd/nginx that require some during init.

  Ahhhh, I can see how that might cause issues. I have made some sysctl tweaks 
and my network always has something going on.
  So I never noticed.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to