IPS 1.2.2 build for Windows Vista
On Tue, Mar 08, 2011, Collins, Jerry wrote:
> Hello,
> My company recently decided to upgrade to the latest FIPS release
> 1.2.2. I've read the Security and User Manual. According to them,
the
> only command we can give is ms\do_fips no-as
Hello,
My company recently decided to upgrade to the latest FIPS release
1.2.2. I've read the Security and User Manual. According to them, the
only command we can give is ms\do_fips no-asm.
While this runs, I see several problems.
1) The build now builds dlls. In the past we did not use
parameter.
The distribution will ALWAYS look for the FIPS files in
/usr/local/ssl/fips-1.0/lib/, since that is where they are put when
you follow the commands given in the Security Policy precisely (as you
must, if you want the validation to 'stick').
-Kyle H
On Fri, Dec 19, 2008 at 2:4
Hello,
I've been trying to upgrade our FIPS compliant software to use the 1.2
release. I have to do this for both Windows and Unix. To date I've
been working on the Unix side but have had a number of problems.
1) Our original version used fipsld to build our executables. However
I've been u
Hello,
I'm having a problem with the fipsld script when trying to line the
fips-1.2 libraries to my programs. This is on a Sun UNIX system.
My problem is during the fingerprint validation. The reference sha1
files, built at the time of the build of the rest of the library have
the filename w
, Collins, Jerry wrote:
> Hello all,
>
> I am having a problem with executables generated with Visual Studio
7
> that use openssl (fips version).
>
Firstly you *have to* using MinGW to build the 1.1.1 validated module.
You can use VC++ to build a more recent snapshot of Ope
Hello all,
I am having a problem with executables generated with Visual Studio 7
that use openssl (fips version).
The problem is that Visual Studio 7 creates a manifest which
references the version of the system dlls to use. Unfortunately, the
version generated when I compile/link doesn't
