On Thu, Sep 15, 2016 at 07:18:52AM +0200, Alex Hultman wrote:
> io_callback(events) {
> if (messages_to_send && (events & OS_WRITABLE)) {
> SSL_write(.);
> if (error) {
> if (error_is_want_read) {
> system_poll &=
Wondering if anyone can recommend a consultant.
I'm having a very specific problem with a lower-level WebRTC library that
I'm unable to fix myself. I have plenty of debugging information, and am
pretty sure it's due to an improperly handled DTLS handshake failure.
Ideally, it would be someone
Hi Thomas,
On Thu, Sep 15, 2016 at 4:26 PM, Thomas J. Hruska
wrote:
>
> The precompiled binary installer variants do this already. If you are using
> default builds, then that's possibly an option.
We prefer to build from source to allow static and dynamic code
On 9/15/2016 3:17 AM, Kim Gräsman wrote:
Hi all,
I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the
Windows build system now produces decorated lib names.
The general pattern seems to be lib_[-].lib where
is only appended for 64-bit builds.
We'd prefer a naked lib name, at
Commands Used:
x86_server:
openssl s_server -cert sercert8192.pem -key serverkey8192 -Verify CAcert.pem
x86_client:
openssl s_client -cert clientcert8192.pem -key clientkey8192 -connect
: -cipher AES128-SHA -
Error log:
x86( Server):
verify error:unable to verify the first certificate
x86
In message <1446abd3-1599-24fe-1340-fc7f3da5e...@wisemo.com> on Fri, 16 Sep
2016 00:12:30 +0200, Jakob Bohm said:
jb-openssl> On 16/09/2016 00:08, Richard Levitte wrote:
jb-openssl> > In message
jb-openssl> >
On 16/09/2016 00:08, Richard Levitte wrote:
In message on
Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman said:
kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed
the
In message
on Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman said:
kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed
the
kim.grasman> Windows build system now produces
- int len = OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
-BIO_write(bio, obj_txt, len);
-BIO_write(bio, "\n", 1);
+OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
+BIO_printf(bio, "%s\n", obj_txt);
Here, used BIO_printf instead of BIO_write, is it solve the issue?
Can you
On 9/15/2016 8:17 AM, Kim Gräsman wrote:
Hi Thomas,
On Thu, Sep 15, 2016 at 4:26 PM, Thomas J. Hruska
wrote:
The precompiled binary installer variants do this already. If you are using
default builds, then that's possibly an option.
We prefer to build from
On 15/09/16 11:44, sivagopiraju wrote:
> I can't upgrade at this stage for my product, So can you give me the fix if
> you have.
The fix for the 1.0.1 version is here:
https://github.com/openssl/openssl/commit/6adf409c7432b90c06d9890787fe56c48f2a16e7
As Rich said 1.0.0 is not supported so the
Hi all,
I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the
Windows build system now produces decorated lib names.
The general pattern seems to be lib_[-].lib where
is only appended for 64-bit builds.
We'd prefer a naked lib name, at least for import libs (the DLL names
are
That’s a bug in the Issuer name length check.
Use the 1.1.0 version.
Cordialement,
Erwann Abalea
> Le 14 sept. 2016 à 14:31, Wouter Verhelst a écrit
> :
>
> Hi,
>
> (this is a resend because my MUA crashed while I tried to send this mail
> earlier. If you get it
I can't upgrade at this stage for my product, So can you give me the fix if
you have.
--
View this message in context:
http://openssl.6102.n7.nabble.com/CVE-2016-2180-tp67815p68371.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
--
openssl-users mailing list
To
14 matches
Mail list logo