On 26 August 2016 at 11:33, Benjamin Kaduk wrote:
> - Because ossltest cooks MD5 to output a constant value, OpenSSL's RNG
> becomes constant.
>
>
> Is it specifically MD5 and not SHA1? That would be worrisome, as I
> thought rand_lcl.h would be setting up for USE_SHA1_RAND by default, not
> md5
>>> How about something like this.. A VC-WIN32-XP target that has
>>> everything needed to make a max compatibility target
>>> When building under VS2012 and above.. (I also tested in VS2015)
>>> adds CFLAGS /arch:IA32 -D_USING_V110_SDK71_
>>> adds BIN_LDFLAGS=/subsystem:console,5.01 /opt:ref
>>
>
From: Sunil Singh [mailto:ekodevelop...@gmail.com]
Sent: Saturday, August 27, 2016 2:42 AM
To: Salz, Rich; openssl-secur...@openssl.org
Subject: Re: [openssl-security] Multiple issue with BIO_new_file Internal
function (potential stack overflow/Crash)
I don't think its right to say that its not
I recently built OpenSSL 1.1.0 x64 debug using Visual Studio 2010, like
this:
perl Configure debug-VC-WIN64A no-asm
nmake
Then I ran the tests
nmake test
At test\recipes\80-test_ssl_old.t a message box popped up with an
assertion failure, I debugged it and saved the information. However when
hello:
i want to use libcurl with openssl, and i build openssl use this cmd:
"perl configure VC-WIN32 no-asm -DOPENSSL_SSL_CLIENT_ENGINE_AUTO=capi
-DOPENSSL_CAPIENG_DIALO"
when i use curl get url,eg "curl -k https://*.com",return the error:
error:89070063:lib(137):CAPI_RSA_SIGN:cant cr
