Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] archer c7 v2, policing, hostapd, test openwrt build
Date: Sun, 22 Mar 2015 18:18:04 -0700	[thread overview]
Message-ID: <CAA93jw4gs2nQvaJ4r+rFCkheYqn-JCi-OyaQfHtOwdOYz9=Z9w@mail.gmail.com> (raw)
In-Reply-To: <4605FB2D-60EC-480A-9C5A-2BFF78560A09@gmail.com>

I don't remember what I did. I remember sticking something in to
improve entropy, and ripping out a patch to hostapd that tried to
manufacture it.

right now I'm merely trying to stablize the new bits - dnssec for
dnsmasq 2.73rc1, babel-1.6 (not in this build) with procd and
ipv6_subtrees and atomic updates, get someone F/T on the minstrel
stuff, and get heads down on per station queuing by mid april. I was
not expecting to make chaos calmer with the last at all and am still
not, and next up is getting some profiling infrastructure in place
that actually works....

On Sun, Mar 22, 2015 at 6:10 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 23 Mar, 2015, at 02:24, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I swear I'd poked into this and fixed it in cerowrt 3.10, but I guess
>> I'll have to go poking through the patch set. Something involving
>> random number obtaining, as best as I recall.
>
> If it’s reseeding an RNG using the current time, that’s fairly bad practice, especially if it’s for any sort of cryptographic purpose.  For general purposes, seed a good RNG once before first use, using /dev/urandom, then just keep pulling values from it as needed.  Or, if cryptographic quality is required, use an actual crypto library’s RNG.
>
>  - Jonathan Morton
>



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

  reply	other threads:[~2015-03-23  1:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  0:24 Dave Taht
2015-03-23  0:31 ` Jonathan Morton
2015-03-23  1:10 ` Jonathan Morton
2015-03-23  1:18   ` Dave Taht [this message]
2015-03-23  1:34 ` Jonathan Morton
2015-03-23  1:45   ` David Lang
2015-03-23  2:00     ` Dave Taht
2015-03-23  2:10     ` Jonathan Morton
2015-03-23  2:15       ` Dave Taht
2015-03-23  2:18         ` Dave Taht
2015-03-23  6:09       ` Sebastian Moeller
2015-03-23 13:43         ` Jonathan Morton
2015-03-23 16:09           ` Sebastian Moeller
2015-03-24  0:00             ` Sebastian Moeller
2015-03-24  0:05               ` Dave Taht
2015-03-24  0:07                 ` Sebastian Moeller
2015-03-24  3:16               ` Jonathan Morton
2015-03-24  7:47                 ` Sebastian Moeller
2015-03-24  8:13                   ` Jonathan Morton
2015-03-24  8:46                     ` Sebastian Moeller
2015-03-29  1:14                     ` Sebastian Moeller
2015-03-29  6:17                       ` Jonathan Morton
2015-03-29 11:16                         ` Sebastian Moeller
2015-03-29 12:48                           ` Jonathan Morton
2015-03-29 14:16                             ` Sebastian Moeller
2015-03-29 15:13                               ` Jonathan Morton
2015-03-23 17:08       ` David Lang
2015-03-23 16:17 ` Sebastian Moeller
2015-03-23 16:27   ` Dave Taht
2015-03-23 17:07     ` David Lang
2015-03-23 18:16       ` Jonathan Morton

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='CAA93jw4gs2nQvaJ4r+rFCkheYqn-JCi-OyaQfHtOwdOYz9=Z9w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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