Am 20. Nov 2012 um 15:42:27 +0100, schrieb Stephen Henson via RT: > > [mtau...@fsmat.at - Tue Nov 20 09:33:34 2012]: > > > > Hello! > > > > I have created a patch which adds a --with-fipsincludedir switch to > > the Configure script. > > If you want to create a FIPS-enabled build, the include files are > > currently looked for in FIPSDIR/include. The value of this option > > makes that directory changeable by the user. > > > > Reason why I did this: I use a seperate install of a FIPS-enabled > > openssl in /usr/local to not interfere with the distribution > > provided version. Since I use openSuse, I have created to RPM files > > (openssl-fipscanister and openssl-fips) which both share the base > > path /usr/local/ssl/fips-2.0. The problem is, that the fips enabled > > openssl overwrites the includes already installed by the > > fipscanister which create a RPM error. My solution is, that I > > install the includes from the fispcanister to a different directory > > (install_canister) and set this directory for the normal build, > > using this patch. > > > > The patch has been tested against openssl-1.0.1c on 32bit Linux > > (openSuse 12.2). > > > > Would setting the FIPSDIR environment variable solve your problem? If > set the module installs to FIPSDIR and not /usr/local/ssl/fips-2.0
No, that won't do. The problem is, that if I set FIPSDIR to /usr/local/ssl/fips-2.0, it automatically looks for the includes in /usr/local/ssl/fips-2.0/include, but I have them in /usr/local/ssl/fips-2.0/include_canister cheers Mathias > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
