On Fri, Mar 14, 2008, Sisyphus wrote: > > >> On Fri, Mar 14, 2008, Sisyphus wrote: >> >>> >>> Rather than digging, I opted for simply linking to my openssl-0.9.8g >>> (static) libcrypto.a by entering the 'test' directory and running: >>> >> >> You can't modify the build process in any way or it violates the security >> policy and the resulting library is not validated. >> > > Heh ... but if I don't modify the build process, then it won't build. (Not > much security in that :-) >
Well if you don't mind the result being not validated you can of course modify the build process, sources anything else in any way you choose. However some of the queries here are from people who *do* want a validated library and for them they have to obey the build instructions verbatim. I don't make the rules, I'm just the messenger here ;-) > The 2 executables that threw up this problem for me are created in a > directory named 'test'. Does that mean they are merely part of the test > suite ? Does 'make test' run ok for you ? > "make test" isn't a necessary part of the approved build procedure as long as: ./config fips make make install works (including compilation completeing without errors) the result is validated. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
