Justin A wrote:
Hi Steve Marquess,
What's the equivalent file for fipscanister.o on windows..?
Let's see ... for the OpenSSL FIPS Object Module v1.1.1/1.1.2 it's
fipscanister.o.
For the upcoming v1.2 it will be fipscanister.lib.
-Steve M.
--
Steve Marquess
Open Source Software Institute
Hi Steve Marquess,
What's the equivalent file for fipscanister.o on windows..?
Thanks,
Justin
--- On Tue, 11/4/08, Steve Marquess <[EMAIL PROTECTED]> wrote:
From: Steve Marquess <[EMAIL PROTECTED]>
Subject: Re: FIPS and new releases of openssl
To: openssl-users@openssl.
ute to any
individuals or organizations, without restriction.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger No-Spam
Sent: Tuesday, November 04, 2008 8:34 AM
To: openssl-users@openssl.org
Subject: FIPS and new releases of openssl
Hello,
In appendix B of t
David Schwartz wrote:
...
Build the FIPS module, then fix the higher-level code, then build the rest
of OpenSSL. So long as don't modify the source before building the FIPS
module, you are fine. You can fix the code that doesn't go in the FIPS
canister without violating FIPS, then link your fix
Roger No-Spam wrote:
Hello,
In appendix B of the openssl FIPS security policy it is stated that
the module must be built with a particular tar file
(openssl-fips-1.1.2.tar.gz) and a hmac hash value for the tar file is
specified. Furthermore it is stated that there shall be no
additions, dele
> Hello,
>
> In appendix B of the openssl FIPS security policy it is stated
> that the module must be built with a particular tar file
> (openssl-fips-1.1.2.tar.gz) and a hmac hash value for the tar
> file is specified. Furthermore it is stated that there shall be
> no additions, deletions, or alt
Hello,
In appendix B of the openssl FIPS security policy it is stated that the module
must be built with a particular tar file (openssl-fips-1.1.2.tar.gz) and a hmac
hash value for the tar file is specified. Furthermore it is stated that there
shall be no additions, deletions, or alterations o
