On Thu, Jan 08, 2009, PGNet wrote: > > ... > Testing SHA-512 ... passed. > Testing SHA-384 ... passed. > if [ -n "libcrypto" ]; then \ > ../util/shlib_wrap.sh ./fips_shatest < SHAmix.r | diff -w > SHAmix.x - ; \ > fi > ERROR:2d06c071:lib=45,func=108,reason=113:file=fips.c:line=274: > 1,129d0 > > I note the ERROR, but no ideas as yet ... Any hints as to why, on this > one box, there's a problem? >
Due to the way the validated code works (keeping the code down to a minimum) error codes from fips standalone utilities give out numerical error codes. You can get the answer with "openssl errstr" or by checking the source file referenced. In this case it is down to the lack of SSE2 on that processor. Due to the limited funding available for validation only certain combinations of options could be tested. So assembly language on x86 requires SSE2 as well. So either use a box supporting SSE2 or use a pure C build (no-asm) which will have poorer performance. 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 majord...@openssl.org
