Is it possible you ran config instead of config fips? I can
reproduce similar errors (different symbols) if I run config instead
of config fips in my build environment.
-David
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of hweeli
Sent:
As far as I know, to have a FIPS certified module, you have to use “./config
fips; make; make install”. Anything else violates the conditions of
certification. This seems to preclude using VC6 to compile FIPS itself.
I was able to do this successfully on Windows using MinGW and MSYS. There
23, 2007, David Hartman wrote:
There is a perl wrapper for the link command that you can use when
linking
with other utilities. I tried using this with VC7 and VC8. I was
successful
linking, and things ran fine in non-FIPS mode. When I tried enabling
FIPS, I
found problems with global statics
Actually, I ran into this as well. The problem is with a command echo
-n ... used to create the list of objects to put into the FIPS archive.
Bourne shell's echo doesn't use the -n, it is perceived as part of what
to echo.
I found I could avoid this problem by using the GNU linker. GNU's
Hi David,
Yes, I did link with fips_premain.c. I specified the compile and link
options for the fipslink.pl script, and included fips_remain.o as an
object.
The problem was that static globals in the gcc-compiled code were not
initialized. For example, I believe there was static int
I recently tried compiling FIPS on Solaris with similar results. What I
found is some of the link options were only understood by the GNU
linker.
I installed the GNU linker along with GCC. GCC has to be compiled to use
specific linkers. Since mine was compiled to use /usr/ccs/bin/ld, I
moved
was able to compile and
install openssl-0.9.7l
without any problems. It's only the fips piece that has an error in the
link step.
Chris Marshall
--- David Hartman [EMAIL PROTECTED] wrote:
I recently tried compiling FIPS on Solaris with similar results. What
I
found is some of the link options were
