btw, you just have to do nmake -f ms\ntdll.mak install under openssl-fips,
it'll copy files to \usr\local\ssl\fips-2.0 in the correct file structure.
--
View this message in context:
http://openssl.6102.n7.nabble.com/Compiling-openssl-fips-in-Windows-tp43439p47313.html
Sent from the OpenSSL -
afx.cpp
FipsSample.cpp
.\FipsSample.cpp(100) : warning C4996: 'fopen': This function or variable may
be unsafe. Consider using fopen_s instead. To disable deprecation, use
_CRT_SECURE_NO_WARNINGS. See online help for details.
C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\includ
inal Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson
Sent: Monday, February 04, 2013 1:58 PM
To: openssl-users@openssl.org
Subject: RE: Compiling openssl fips in Windows
>From: owner-openssl-us...@openssl.org On Behalf Of Jon Evers
&
sl-us...@openssl.org] On Behalf Of Memmott, Lester
Sent: Monday, February 04, 2013 2:51 PM
To: openssl-users@openssl.org
Subject: RE: Compiling openssl fips in Windows
Jon,
Regarding:
According to my interpretation of the documentation, it should be
included in libeay32.dll:
Section 2.4.2
Note
Jon,
Regarding:
According to my interpretation of the documentation, it should be included in
libeay32.dll:
Section 2.4.2
Note that except in the most unusual circumstances the FIPS Object Module itself
(fipscanister.o) is not linked directly with application code.
Section 4.3.3
The resulting F
>From: owner-openssl-us...@openssl.org On Behalf Of Jon Evers
>Sent: Friday, 01 February, 2013 17:45
>I'm trying to link an application that will use openssl and fips.
>I'm getting linker errors [using] MS Visual Studio 2008.
>I'm trying to link the DLL, lib32eay.dll.
Did you put libeay32.dll in
ssl.org
Subject: RE: Compiling openssl fips in Windows
Regarding:
C:\temp\nma0452:
setargv.obj d:\work\ssl\ved\Debug\VED.obj
d:\work\ssl\ved\Debug\stdafx.obj d:\work\ssl\ved\Debug\fips_premain.obj
d:\Work\SSL\openssl-1.0.1c\out32dll\libeay32.lib ws2_32.lib gdi32.lib
advapi32.lib crytp32
Regarding:
C:\temp\nma0452:
setargv.obj d:\work\ssl\ved\Debug\VED.obj d:\work\ssl\ved\Debug\stdafx.obj
d:\work\ssl\ved\Debug\fips_premain.obj
d:\Work\SSL\openssl-1.0.1c\out32dll\libeay32.lib ws2_32.lib gdi32.lib
advapi32.lib crytp32.bli user32.lib
I’m not sure but did you link in fipscanister.l
On Fri, Jun 12, 2009, Carl Furner wrote:
> I need the validated version for fips For the contract I am working
> on.
>
>
>
>
>
> 1) Can I compile OpenSSL fips using VC 9 and still get a
> validated\certified version?
>
>
Yes, as long as you obey the rest of the security policy
Hi All,
When i was building openssl 9.8h , i got this error ..
(cd ..; gmake DIRS=test TESTS=alltests all)
gmake[1]: Entering directory `/joshi/openssl-0.9.8h_final'
making all in test...
gmake[2]: Entering directory `/joshi/openssl-0.9.8h_final/test'
xlc_r -I.. -I../include -DOPENSSL_THREADS -
> This among other things requires the application to enable FIPS
> mode which a
> typical application will not do. One of several effects of
> entering FIPS mode
> is to disable the use of non-FIPS algorithms: this may cause
> problems where
> the application expectes to use such algorithms and c
Wei:
Here's what I think I've learned about this question.
I think if you compiled openssl-fips-1.1.1 with "config fips; make; make
install" the result would
be an openssl library that was fips certified.
Getting libcurl to make proper use of it would then be a question of whether
libcurl make
On Fri, Feb 23, 2007, Wei Weng wrote:
> Chris: Thanks for the reply.
>
> Here is the thing I want: I need to build a openssl library that is fips
> capable so that I can link libcurl against the library, since libcurl
> uses openssl library to do the decode/encode stuff.
>
> I am guessing that
Chris: Thanks for the reply.
Here is the thing I want: I need to build a openssl library that is fips
capable so that I can link libcurl against the library, since libcurl
uses openssl library to do the decode/encode stuff.
I am guessing that I will need to build my own openssl library that
Wei:
My current guess is that if all you are trying to do is get an openssl utility
that is FIPS
certified, then doing
./config fips
make
make install
from inside the top level directory of openssl-fips-1.1.1 is all that is
required.
If you want an openssl utility of a more recent 0.
On Thu, Feb 15, 2007, David Hartman wrote:
> Hi Chris, Wei,
>
> The normal OpenSSL config and build scripts seem to be different from
> the FIPS one. My original attempts at building FIPS didn't run into a
> problem until the steps to link fipscannister.o itself. This wouldn't be
> an issue with
ted with the OS doesn't understand the
options supplied for GNU's linker.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Marshall
Sent: Thursday, February 15, 2007 2:10 PM
To: openssl-users@openssl.org
Subject: RE: compiling openssl-fi
David:
Thanks for the info. Interestingly enough, I 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
Wei:
I saw your post. I don't know whether it is correct or not. You are further
along that I am ;-)
I'll try the procedure in your post once I get my problem solved. I'm still
reading the OpenSSL
FIPS Object Module Guide, which covers what steps you have to go through for
the result to be
c
Hi. Sorry I can not answer your question, but it seems that you are the
only one that is working on getting openssl-fips-1.1.1 to work these
days, so I had to bug you for some trivial questions. :)
Do you think the process I had gone into making openssl-fips-1.1.1 work
is correct? (I do realiz
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 that
21 matches
Mail list logo
