On 02/13/2013 06:58 PM, Zeke Evans wrote:
> Hi,
>
> Building the FIPS module on sparc 64-bit is generating a 32-bit
> binary. The following message is in the output:
>
> WARNING! If you wish to build 64-bit library, then you have to
> invoke './Configure solaris64-sparcv9-cc' *manually*.
>
> My understanding is that building with that command is not allowed.
> Another work around is to call
>
> KERNEL_BITS=64 ./config no-asm
>
> Is this permissible?
Yes, with two caveats:
1) The Security Policy documents the command as "./config", not
"./config no-asm".
2) For conformity to the Security Policy I would invoke the "./config"
command on a separate line, e.g.
$ export KERNEL_BITS=64
$ ./config
The fact that these commands are functionally equivalent to what you are
doing is irrelevant for compliance purposes; those Security Policy
instructions should be taken literally. Software development "common
sense" does not apply.
Note the formal testing used this enormously complicated and
sophisticated script to set the environment:
http://opensslfoundation.com/testing/validation-2.0/platforms/solaris/setenv-sparc-64.sh
-Steve M.
--
Steve Marquess
OpenSSL Software Foundation, Inc.
1829 Mount Ephraim Road
Adamstown, MD 21710
USA
+1 877 673 6775 s/b
+1 301 874 2571 direct
marqu...@opensslfoundation.com
marqu...@openssl.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
