Re: [openssl-dev] [openssl.org #4690] Bug in OpenSSL 1.0.2j ssl_accept

Hallo Steve, since the output comes from an in production system, we doesn't have debugging symbols there. I'll try to setup a second machine with the same configuration and use debugging symbols there. Before upgrading to 1.0.2j we use 1.02h-r2 (each marked as "stable" in Gentoo portage

[openssl-dev] [openssl.org #4690] Bug in OpenSSL 1.0.2j ssl_accept

On Wed Sep 28 19:44:49 2016, mich...@michsoft.de wrote: > In addition to my message I send you my gdb backtrace: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x71413700 (LWP 13663)] > 0x76ba4e87 in sk_value () from /usr/lib64/libcrypto.so.1.0.0 >

[openssl-dev] [openssl.org #4689] Fwd: Bug in OpenSSL 1.0.2j ssl_accept

In addition to my message I send you my gdb backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x71413700 (LWP 13663)] 0x76ba4e87 in sk_value () from /usr/lib64/libcrypto.so.1.0.0 (gdb) backtrace #0 0x76ba4e87 in sk_value () from

Re: [openssl-dev] About Chinese crypto-algorithms

Hello Robin, On Wed, Sep 28, 2016 at 3:44 PM, Salz, Rich wrote: > (I subscribed you to openssl-dev; I hope it works.) > > ISO standards are “pay to play.” That is, any member organization can get > something as an ISO standard with not much effort. :) > > >> "I strongly

Re: [openssl-dev] [openssl.org #4676] Error converting to p12 crt

You did not cut/paste the command line properly because you wrote "-in -inkey" which is wrong. Or maybe that is your error? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4676 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] SSLKEYLOGFILE Support

> [0]: > https://commondatastorage.googleapis.com/chromium-boringssl-docs/ssl.h.html#SSL_CTX_set_keylog_callback That seems like a reasonable thing to put into the next release. -- Senior Architect, Akamai Technologies Member, OpenSSL Dev Team IM: richs...@jabber.at Twitter: RichSalz --

Re: [openssl-dev] SSLKEYLOGFILE Support

> On 28 Sep 2016, at 11:11, Cory Benfield wrote: > > So what do the OpenSSL developers think? Do we need the compile flag, or is > some lower bar sufficient? It was brought to my attention that BoringSSL takes an alternative approach to this problem: they allow users to

[openssl-dev] [openssl.org #4687] Bug in apps/req.c introduced in openssl 1.0.2i

Hi, When trying to generate a self signed certificate from a previously generate csr with the command line: openssl req -x509 -key privkey.pem -in csr.pem -out selfsigned.pem it now prompts for country code etc. which is stored in the CSR. This change in behavior was introduced by: commit

[openssl-dev] [openssl.org #4688] bug since openssl1.0.1i

Hello, there is a bug in openssl since openssl1.0.1i I am compiling under Solaris 10 with CC from SolarisStudio 12.3. The problem is not the compiler, it is the implementation of the new test dtlstest. I always did "make dclean" and up to openssl1.0.1h there was no problem, since

[openssl-dev] SSLKEYLOGFILE Support

All, Some time ago I posted noting that it would be useful to have the SSLKEYLOGFILE environment variable supported by OpenSSL. I lost track of that request, and have since noticed that a patch that would have added support for that environment variable[0] was closed, with Rich asking for an

[openssl-dev] Input on renegotiation behaviour

I recently implemented some tests for renegotiation that turned up a discrepancy between the way TLS and DTLS work. If a server sends a HelloRequest to the client, then the client responds by initiating a renegotiation handshake. We support two forms of renegotiation handshake: normal and