On 22/08/2016 22:33, Scott Ware wrote:
On Mon, Aug 22, 2016 at 3:04 PM, Jakob Bohm >wrote:
On 22/08/2016 20:09, Scott Ware wrote:
We use libeay32.dll and ssleay32.dll from
I am having a problem where FIPS_incore_fingerprint is failing to generate the
same signature as our build script.
If I set a breakpoint in FIPS_incore_fingerprint it appears that p1-p4 are all
being set correctly. If I dump memory for each section (p1-p2 and p3-p4) and
concatenate the binary
On Mon, Aug 22, 2016 at 3:04 PM, Jakob Bohm wrote:
> On 22/08/2016 20:09, Scott Ware wrote:
>
>> We use libeay32.dll and ssleay32.dll from https://slproweb.com/products/
>> Win32OpenSSL.htmlin our applications and we recently moved from version
>> 1.0.2a to 1.0.2g and now
I've done a custom build of OpenSSL where I ran Configure with "no-ssl2" and
"no-ssl3". I'd like to disable TLS1 and 1.1 if possible. Will the no-tls1
option disable just TLS1 or all TLS1.x protocols?
Thanks,
ScottN
--
openssl-users mailing list
To unsubscribe:
On 22/08/2016 20:09, Scott Ware wrote:
We use libeay32.dll and ssleay32.dll from
https://slproweb.com/products/Win32OpenSSL.htmlin our applications and
we recently moved from version 1.0.2a to 1.0.2g and now on a few
machines running a AMD Geode processor we are getting "Unhandled
exception
We use libeay32.dll and ssleay32.dll from
https://slproweb.com/products/Win32OpenSSL.html in our applications and we
recently moved from version 1.0.2a to 1.0.2g and now on a few machines
running a AMD Geode processor we are getting "Unhandled exception at
0x005904dc (libeay32.dll) in Test.exe: