For contrast, here is a 'rngtest' run against a
3.1.8 Linux kernel with /dev/random enhanced by
the output of a STMicroelectronics ST33 TPM PRNG
(via 'rngd' v4).
bits received from input: 62380032
FIPS 140-2 successes: 3115
FIPS 140-2 failures: 4
FIPS 140-2(2001-10-10) Monobit: 0
FIPS 140-2(2001-1
I see that CryptGenRandom() does not appear
to have parameters to detect or control
the quality of entropy.
So possibly the correct solution to this
issue would be to eliminate
/dev/random
and just leave
/dev/urandom
in place. 'openssl' apparently uses /dev/urandom.
If someone needs
Hello,
While poking around TRNG quality I came
across this apparent issue:
/dev/random does not block, emits poor entropy
Running 1.7.17 but see no updates in the
1.7.18 thru 1.7.25 Changelog entries
regarding /dev/random.
Due to 'argp' library issues I could not
compile 'rngtest' under Cygw
Fixes the CTRL-C problem and the point
behind it all, running a critical build
script, work as well.
>
>stephan($0.02);
>
>-Original Message-
>From: cygwin-owner at cygwin dot com
>On Behalf Of starlight.2013z3 at binnacle dot cx
>Sent: Wednesday, July 31, 2013 10:26 AM
>
Well I uncovered a serious regression
and expressed a willingness to track
down the cause.
However your nasty reply and bad attitude
assures that I will defintiely not help
now.
At 01:21 PM 7/31/2013 -0400, Christopher Faylor wrote:
>You are right in assuming that newer DLLs should
>work with old
Hello,
Have been running 1.7.16 for some time
and living with the annoying CTRL-C hang
bug.
Tried swapping in cygwin1.dll cyglsa.dll
and cyglsa64.dll from 1.7.22-1 without
(thankfully) updating the entire CYGWIN
release.
The 22-1 DLLs fix the CTRL-C problem,
but cause a high-intensity parallel
b
6 matches
Mail list logo