linux-kernel - Re: [PATCH] crypto: force reset of cprng on allocation

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: <20090128042107.GC13157@gondor.apana.org.au>
Date:	Wed, 28 Jan 2009 15:21:07 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Neil Horman <nhorman@...driver.com>
Cc:	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto: force reset of cprng on allocation

On Fri, Jan 23, 2009 at 11:50:27AM -0500, Neil Horman wrote:
> pseudo RNGs provide predictable outputs based on input parateters {key, V, DT},
> the idea behind them is that only the user should know what the inputs are.
> While its nice to have default known values for testing purposes, it seems
> dangerous to allow the use of those default values without some sort of safety
> measure in place, lest an attacker easily guess the output of the cprng.  This
> patch forces the NEED_RESET flag on when allocating a cprng context, so that any
> user is forced to reseed it before use.  The defaults can still be used for
> testing, but this will prevent their inadvertent use, and be more secure.
>    
> Signed-off-by: Neil Horman <nhorman@...hat.com>

Applied to cryptodev.  Thanks Neil!
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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/