From: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.13-2 released
Date: Tue, 01 Oct 2013 17:28:34 +0300 [thread overview]
Message-ID: <524ADC12.4090106@etorok.net> (raw)
In-Reply-To: <CAA93jw7RVU2GaTypRfv0zQr_OOihPkEpt3i_eFmYOE7eSwynhg@mail.gmail.com>
On 10/01/2013 04:42 PM, Dave Taht wrote:
> + Proved it is possible to build an OS release on a "Narrowboat"
> - but not test one without hacking at the 12v power supply off the solar panel
> + merge with openwrt head
> + dnsmasq 2.67test17
> + ipv6subtrees now part of 3.10.12
> + htb adsl fixes also
> + Simon kelly is starting to finalize dnsmasq 2.67 now that summer is over
>
> - still no fix for the sysupgrade bug
> - Most of the get_cycles() and /dev/random keruffle has settled down
> but I did not fold the latest patchset for that into this. The
> discussion on PRNGs was very illuminating and worth reading.There were
> multiple threads on this topic on lkml, this is one:
>
> https://lkml.org/lkml/2013/9/10/188
Does this mean that we can get rid of running rngd the wrong way? [1]
[1] Currently cerowrt runs rngd -r /dev/urandom, which is exactly what should not be done
,as it would essentially make /dev/random non-blocking like /dev/urandom and fool userspace into generating keys without enough entropy, etc.:
https://lwn.net/Articles/525459/
Best regards,
--Edwin
prev parent reply other threads:[~2013-10-01 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 13:42 Dave Taht
2013-10-01 14:28 ` Török Edwin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524ADC12.4090106@etorok.net \
--to=edwin+ml-cerowrt@etorok.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox