1) I do not have the source from the CD yet, that is on the way.
2) I've looked, and I do not see a listing of FIPS qualified platforms. I
am compiling with the following specs:
--gcc version 4.4.3
--cross compile mips-openwrt-linux-uclibc
--arch mips32r2
--tune 24kc
--Hardware Atheros (AR7161) MIPS 24K
Thanks,
Michael Johnson
From: Patrick Patterson <ppatter...@carillon.ca>
To: openssl-users@openssl.org
Date: 07/25/2012 05:54 AM
Subject: Re: Cross compiling openssl + openssl-FIPS for
mips-openwrt-linux-uclibc
Sent by: owner-openssl-us...@openssl.org
I would ask two questions:
1) Are you using the distributed source from the CD?
2) Is that particular MIPS platform one of the platforms for which the
FIPS qualifications applies?
If 1), you need to do this (not that it will necessarily solve your
problem :)
If not 2), then you'll need to get a change letter, and in that change,
you can ask for the compiler line tweak.
Have fun!
Patrick.
On 2012-07-24, at 5:25 PM, majoh...@rockwellcollins.com wrote:
> Hey,
>
> I'm trying to get a FIPS certified openssl, and after
>
> When I compile normally ("./config"), I get an error saying that
> "libcrypo.so.1.0.0 is not cross-compiler aware"
>
> However, if I run config for the FIPS module like so:
>
> ./config -DFIPS_REF_POINT_IS_CROSS_COMPILER_AWARE
>
> Everything compiles normally. So my problem is that it's not FIPS
> certified when the config line is not "./config [no-asm]". Does anyone
> know what the issue is or how I can work around it without losing my
FIPS
> cert?
>
> Thanks,
> Michael Johnson
---
Patrick Patterson
Chief PKI Architect
Carillon Information Security Inc.
http://www.carillon.ca
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
