Yes, I know it sounds crazy. Our product has historically linked everything
statically into one giant executable and also one medium size shared library
for customer linking. What I need to do is statically link in the FIPS
capable libraries into a dynamic library, in this case on a .so (on windows
Linking the FIPS capable libraries to our code is proving to be a real pain
in the butt. The problem stems from the fact that long before I arrived it
was decided that everything is to be linked statically. So that means that
fipsld is needed. To compound things our code is c++ and compiled using g
On 12/20/07 9:16 PM, "Ben Sandee" <[EMAIL PROTECTED]> wrote:
> On Dec 20, 2007 9:47 PM, Jacob Barrett <[EMAIL PROTECTED]> wrote:
>> Following the instructions in the FIPS users guide I can build the FIPS
>> Object Module just fine. What I can't
Following the instructions in the FIPS users guide I can build the FIPS
Object Module just fine. What I can't get to work is the Windows DLL build
of OpenSLL with the FIPS module. I can build that static libraries with FIPS
and the DLL without FIPS. When I try to build the dll with FIPS though I ge
Is there anyway to allow SSLv3 on some SSL_CTXs? I realize that FIPS only
allows TLS, but I don't need all my services to use FIPS to satisfy my
requirements, so it would be nice to allow some to run with lowered
standards, like SSLv3. Any chance that is a special method to allow this?
Thanks,
Jak
On 12/19/07 11:06 AM, "Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 19, 2007, Jacob Barrett wrote:
>> Can this be overcome within the terms of the security policy or am I SOL on
>> Intel Macs?
>>
>
> No you can't change anyth
I am unable to compile the FIPS module on an Intel Mac because the Configure
script incorrectly adds the -DB_ENDIAN flag to the cc args. I have changed
it for now in the Configure script, but fear that invalidates the FIPS
security policy. Any help is much appriciated.
Can this be overcome within
