Hey all-
Ok, so I've got a story behind this one. It was recently called to my
attention that the ansi cprng is missing an aspect of its compliance requrements
for FIPS-140. Specifically, its missing a behavior in its continuous test.
When the CPRNG produces random blocks, the firrst
patch 1/3: Add flags infrastructure to rng api
This patch adds api calls for get/set flags calls to the crypto rng api. This
api allows algorithm implementations to register calls to respond to flag
settings that are global and common to all rng's. If a given algorithm has no
external flags that
patch 2/3: Update testmgr code to place any rng it tests in TEST_MODE
This patch instructs the testmgr code to place all rng allocations that it makes
into test mode, so that in the event that it has internal mechanisms that may
affect the testing of the RNG, they won't affect the outcome of the
patch 3/3: modify cprng to make contnuity check fips compliant and allow for a
disabling of the continuity test when the RNG is placed in FIPS mode
Signed-off-by: Neil Horman nhor...@txudriver.com
ansi_cprng.c | 56 +++-
1 file changed, 51
As reported by Frans Pop the new global macro W on ARM which is included
via
|arch/arm/include/asm/uaccess.h:20
|include/linux/uaccess.h:5
|include/linux/crypto.h:26
|crypto/cast6.c:23
leads to a build error because the crypto/cast6.c defines a function
which is named W.
Reported-by: Frans Pop
On Wed, Sep 16, 2009 at 07:58:12PM +0200, Sebastian Andrzej Siewior wrote:
leads to a build error because the crypto/cast6.c defines a function
which is named W.
W has nothing to do with the access size, so this change makes it _really_
confusing. What it's about is telling the compiler to use
On 09/16/2009 12:11 PM, Neil Horman wrote:
patch 1/3: Add flags infrastructure to rng api
This patch adds api calls for get/set flags calls to the crypto rng api. This
api allows algorithm implementations to register calls to respond to flag
settings that are global and common to all rng's. If
On 09/16/2009 12:04 PM, Neil Horman wrote:
Hey all-
Ok, so I've got a story behind this one. It was recently called to my
attention that the ansi cprng is missing an aspect of its compliance requrements
for FIPS-140. Specifically, its missing a behavior in its continuous test.
When the
On 09/16/2009 12:13 PM, Neil Horman wrote:
patch 2/3: Update testmgr code to place any rng it tests in TEST_MODE
This patch instructs the testmgr code to place all rng allocations that it makes
into test mode, so that in the event that it has internal mechanisms that may
affect the testing of
On 09/16/2009 12:25 PM, Neil Horman wrote:
patch 3/3: modify cprng to make contnuity check fips compliant and allow for a
disabling of the continuity test when the RNG is placed in FIPS mode
Signed-off-by: Neil Hormannhor...@txudriver.com
Acked-by: Jarod Wilson ja...@redhat.com
--
Jarod
On Wed, 2009-09-16 at 19:58 +0200, Sebastian Andrzej Siewior wrote:
As reported by Frans Pop the new global macro W on ARM which is included
via
|arch/arm/include/asm/uaccess.h:20
|include/linux/uaccess.h:5
|include/linux/crypto.h:26
|crypto/cast6.c:23
leads to a build error because the
11 matches
Mail list logo