Ted writes:
> [...]
>
> As far as yarrow versus the current design, I've certainly looked at
> yarrow, and I've certainly considered adding some of yarrow's design
> into my /dev/random implementation. Given that I strongly recommend
> that the 512 bytes of entropy be saved from /dev/random at
Ted writes:
> A couple of comments here. It was always the intention that
> /dev/random be 0666, and in my implementation, writing to
> /dev/random mixed the input into the entropy pool *without* changing
> the entropy estimate.
I see. This is not clear.
We recently set it /dev/random to grou
Mark writes:
> Adam writes:
> > OK, I agree that that's an area where yarrow offers better protection.
> > But it's not like Ted's code is broken or anything. We would break
> > things using /dev/random by switching as is to yarrow, so this is why
> > I don't like it: we're trying to improve thi
Jeroen writes:
> > > Twofish in abrest Davies-Meyer mode is going to blow away BF-CBC-256
> > > pseudo 256 bit block cipher Davies-Meyer performance wise, because of
> > > the key agility.
>
> But Twofish is not neccessarily the best choice. Yes, it's being
> pushed by Bruce Schneier but that's
Mark writes:
> [...]
> FreeBSD is using an earlier version of T'so's code; I beiieve he
> improved it later, but it has no (or little) backtracking protection,
> and can be too easily attacked "from both sides".
OK, I agree that that's an area where yarrow offers better protection.
But it's not
Mark writes:
> > You really can't use yarrow to implement /dev/random as it is.
> > [...]
>
> OK; what then? The existing MD5 based system is very attackable, and
> protects itself very poorly.
My argument for linux is leave it as it is, and see if we can persuade
the yarrow authors to change
Mark writes:
> > I'm hoping to persuade the yarrow designers of the importance of
> > supporting /dev/random semantics for the unix community acceptance.
> > John Kelsey and I had some discussions along the lines of feeding
> > /dev/random output into yarrow, which I notice someone on here
> > co
[try again this foobared the first time -- apologies for duplicates]
[If this bounces because I am not a list member, could I trouble one
of you to forward it to the list? -- Thanks]
Hi all
We've been implementing yarrow at zeroknowledge also. I just read
through the freebsed-current archives
