On 09/29/2016 12:40 PM, Troy Smoke wrote:
> I am in the position of evaluating products that have (or claim to have)
> implemented the OpenSSL FIPS module.
>
> I would like to be able to be able to run a command or run the FIPS
> self-test on command, for the purpose of verifying if OpenSSL is
>
I am in the position of evaluating products that have (or claim to have)
implemented the OpenSSL FIPS module.
I would like to be able to be able to run a command or run the FIPS
self-test on command, for the purpose of verifying if OpenSSL is operating
in FIPS mode.
This may not be important for
On 09/27/2016 10:57 AM, Zeke Evans wrote:
>> ...
>
> The fixed base address requirement causes problems for large Windows
> x86 applications and there isn't a great work around. It isn't clear
> to me if item 2 " Support compilation in various forms" will address
> this or not. An option to
> As always, if you don't care about FIPS 140 then count yourself lucky and
> move on.
>
> Work on the new FIPS module has so far taken a backseat to higher priority
> topics like the 1.1 release and security vulnerabilities, but we should start
> to
> make some progress soon. I've put together
On 27/09/2016 15:41, Steve Marquess wrote:
As always, if you don't care about FIPS 140 then count yourself lucky
and move on.
Work on the new FIPS module has so far taken a backseat to higher
priority topics like the 1.1 release and security vulnerabilities, but
we should start to make some
As always, if you don't care about FIPS 140 then count yourself lucky
and move on.
Work on the new FIPS module has so far taken a backseat to higher
priority topics like the 1.1 release and security vulnerabilities, but
we should start to make some progress soon. I've put together a rough
wiki
