linux-kernel - Re: Updated scalable urandom patchkit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20151021181016.25249.qmail@ns.horizon.com>
Date:	21 Oct 2015 14:10:16 -0400
From:	"George Spelvin" <linux@...izon.com>
To:	andi@...stfloor.org, linux@...izon.com
Cc:	ahferroin7@...il.com, jepler@...ythonic.net,
	linux-kernel@...r.kernel.org, linux@...musvillemoes.dk,
	tytso@....edu
Subject: Re: Updated scalable urandom patchkit

> Can we just use my multi pool patch for now? It works and is actually scalable
> and does not require any new "cryptographic research" or other risks.

To clarify, it's actually quite easy to come up with something that works,
cryptographically.  All the discussion is:
1) Erring on the side of public discussion for a security-sensitive area, and
2) Trying to find "The Right Thing" among the many workable solutions.

Earlier, Ted seemed to be interested in more significant changes like
replacing sha_transform and "abuse mitigation mode", so I've been
thinking expansively.  The immediate plans aren't necessarily quite
as complex.

Mostly, it's an embarrassment of ways to do it, and trying to find
a reason to choose one over the other.  I wrote one very quickly, said
"I can do better", thought about coding that up, thought of an even
better solution, and decided to post the performance-affecting part
while I played donkey-between-two-piles-of-hay.

> or other risks.

Ted gets to decide, but my objection is that the already-sparse entropy
supply is considerably diluted.  That *is* a risk.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/