full-disclosure - Re: SecureW2 TLS security problem

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: <iluhdbuwwic.fsf@latte.josefsson.org>
Date: Thu Oct  6 15:30:49 2005
From: jas at extundo.com (Simon Josefsson)
Subject: Re: SecureW2 TLS security problem

Yvan Boily <yboily@...il.com> writes:

> The default random number generator provided with Windows XP, 2003,
> and Longhorn, is RtlGenRandom(PVOID,ULONG)
> ; this is an undocumented API that is called by
> CryptGenRandom(HCRYPTPROV, DWORD, BYTE*).

SecureW2 is using CryptGenRandom now.

> It uses significantly better sources of entropy than clock information
> and process & thread ids.

Are you aware of a quantification of the improvement?  Having many
entropy sources only inspire more confidence if the additional entropy
sources provide any entropy.  It is not clear to me that there is
enough entropy in the listed sources to provide with good random
numbers.  Frankly, the list of entropy sources is so huge it appears
as if it is meant to scare you away from scrutinizing each single
entropy source.  It is not clear whether the PRNG is ever re-seeded.

Thanks,
Simon