> On Mar 28, 2016, at 10:24 PM, Aaron wrote:
>
> It is very stratforward to repro the issue. Take platform linux_x86-64 as an
> example, the repro steps are as follows.
>
> cd openssl-1.0.2g
> make clean
> ./Configure no-idea no-mdc2 no-rc5 no-ec2m fips -m64 no-asm linux-x86_64
> make depen
Greetings.
I am using OpenSSl 1.0.2f on various platforms including Solaris, Linux,
RS6000, ibmplinux, HPIA and Windows. Now I am going to upgrade to OpenSSL
1.0.2g. However I hit a test failure when building and tesing 1.0.2g. The
issue occurs on all my platforms except Windows which I haven't t
>What platform are you building? Is it a native or cross compile?
>You'd get that behaviour if fipsld isn't linking the binaries properly.
Thanks Steve. I am on centos 6, native compile. I saw " /libcrypto.so is not
cross-compiler aware." with fipsld linking until introducing -exe option to
in
On 3/25/16, 17:17 , "openssl-users on behalf of Viktor Dukhovni"
wrote:
>>If I ask “is your passport valid”, I expect to be able to repeat this
>> question and (as long as this all is within a reasonably short time) get
>> exactly the same answer.
>
>The result of X509_verify_cert() is not just
In 1.0.2 and later, most of the files in ${BUILD_DIR}/include/openssl
are supposed to be copies/symlinks to file of the same name elsewhere
in the OpenSSL source, for instance the ones you mentions should be
links to files in subdirectories under ${BUILD_DIR}/crypt.
However in your case, I suspec