That's a useful thing to try - given the earlier mismatch, I suspect that it
may be something in the hash calculation that's not quite lining up and causing
the signature match to fail. thanks for the suggestion .. N
________________________________________
From: openssl-users [openssl-users-boun...@openssl.org] on behalf of Viktor
Dukhovni [openssl-us...@dukhovni.org]
Sent: February 27, 2016 1:28 PM
To: openssl-users@openssl.org
Subject: Re: [openssl-users] [openssl-dev] Failed TLSv1.2 handshake with
error 67702888--bad signature
> On Feb 27, 2016, at 4:25 PM, Nounou Dadoun <nounou.dad...@avigilon.com> wrote:
>
> I agree but that's not the side I'm working on; the client is already widely
> distributed and if we can identify that as the interop problem then I can
> make an argument to the client team to upgrade but that doesn't solve the
> currently deployed problem ... N
Given that your server is on ARM, which is not yet a widely used platform for
OpenSSL 1.0.2, most
likely the issue is there. So disabling ASM on the server side is worth a try.
Also test your client against non-ARM 1.0.2d servers...
--
Viktor.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
