On Fri, 25 Dec 2009 13:38:10 -0800
Doug Barton wrote:
> Robert Watson wrote:
> > I'll point Mark Murray at this thread and see if we can get him to
> > opine some on the current design choices and any potential changes
> > to address them. I was interested by your observation that the
> > boot-t
Robert Watson wrote:
> I'll point Mark Murray at this thread and see if we can get him to opine
> some on the current design choices and any potential changes to address
> them. I was interested by your observation that the boot-time dumping
> of bits into /dev/random may overflow the buffering --
On Thu, 24 Dec 2009, RW wrote:
And also according to Schneier it is a good idea to save state of the PRNG
and restore it on boot to make it "more seeded".
In the default configuration, we save some PRNG output every few minutes
(using cron) to a file in /var so that it can be re-injected int
On Thu, 24 Dec 2009 19:48:43 + (GMT)
Robert Watson wrote:
> On Thu, 24 Dec 2009, Paul Graphov wrote:
>
> > And also according to Schneier it is a good idea to save state of
> > the PRNG and restore it on boot to make it "more seeded".
>
> In the default configuration, we save some PRNG outp
On Thu, 24 Dec 2009, Paul Graphov wrote:
And also according to Schneier it is a good idea to save state of the PRNG
and restore it on boot to make it "more seeded".
In the default configuration, we save some PRNG output every few minutes
(using cron) to a file in /var so that it can be re-inj
Dont these lines (random_yarrow_init function) make it available to set
"seeded" to zero?
SYSCTL_ADD_PROC(&random_clist,
SYSCTL_CHILDREN(random_sys_o),
OID_AUTO, "seeded", CTLTYPE_INT | CTLFLAG_RW,
&random_systat.seeded, 1, random_check_boolean, "I",
random_systat.seeded is exported to sysctl? isn't it?
In this case If somebody resets it to zero, some "read" goest to "block" and
before acquiring mutex it is reseeded, setting it to true, block will never
leave the cycle.
2009/12/24 RW
> On Thu, 24 Dec 2009 15:45:15 +0300
> Paul Graphov wrot
On Thu, 24 Dec 2009 15:45:15 +0300
Paul Graphov wrote:
> Hello guys,
>
> I've looked at FreeBSD 8.0 cryptographically secure pseudorandom
> numbers generator and have a question. It looks like a bug but I'am
> not sure.
>
> In file sys/dev/randomdev.c, function random_read:
>
> if (!ra
Hello guys,
I've looked at FreeBSD 8.0 cryptographically secure pseudorandom
numbers generator and have a question. It looks like a bug but I'am
not sure.
In file sys/dev/randomdev.c, function random_read:
if (!random_systat.seeded)
error = (*random_systat.block)(flag);
9 matches
Mail list logo
