Can anyone shed light on why these APIs are disabled in FIPS mode? They
involve operations that must be implemented within the boundary of the FIPS
crypto module? It seems like disabling them is intended to prevent mistakes
from developers trying to write their own AES mode implementations?
Thank
Looks like there is a relevant discussion here
http://groups.google.com/group/mailing.openssl.users/msg/fa55b6bac4f91d8f
_
_
From: owner-openssl-us...@openssl.org [owner-openssl-us...@openssl.org] On
Behalf Of David Weidenkopf [dweidenk...@cococorp.com]
Sent
Hello, has anyone ever tried to incorporate the FIPS crypto module(sepcifically
the crypto algorithms) into a kernel module? Or the feasibility of such an
effort? The idea is that you then have FIPS capable crypto in the kernel. The
kernel crypto api, as far as I can tell, is designed to allow f
Hello, has anyone ever tried to incorporate the FIPS crypto module(sepcifically
the crypto algorithms) into a kernel module? Or the feasibility of such an
effort? The idea is that you then have FIPS capable crypto in the kernel. The
kernel crypto api, as far as I can tell, is designed to allow f
