[openssl-users] OpenSSL sending close_notify right afterresponding to a heartbeat request

Jakob Bohm jb-openssl at wisemo.com
Tue Mar 28 18:48:27 UTC 2017

Just to clarify: Does it respond to the heartbeat before closing
the session, or does it just close the session when you try to
trigger the heartbeat/bleed code?

On 28/03/2017 16:29, Kaja Mohideen wrote:
> Thanks for the response, Micheal Wojcik. Any idea what is making 
> OpenSSL close the session after responding to Heartbeat request?
> ------------------------------------------------------------------------
> From: Michael Wojcik <mailto:Michael.Wojcik at microfocus.com>
> Sent: ‎28-‎03-‎2017 07:46 PM
> To: openssl-users at openssl.org <mailto:openssl-users at openssl.org>
> Subject: Re: [openssl-users] OpenSSL sending close_notify right 
> afterresponding to a heartbeat request
> > From: openssl-users [mailto:openssl-users-bounces at openssl.org] On Behalf
> > Of R Kaja Mohideen
> > Sent: Monday, March 27, 2017 13:55
> >
> > I'm surprised to see that I'm not able to get the caller details using
> > backtrace. Is it due to architecture of OpenSSL or something which
> > makes OpenSSL to use a new thread for invoking ssl_shutdown?
> I suspect it's due to compiler optimization, a lack of symbols in the 
> caller, or some other generic obstacle to backtracing, and not 
> anything OpenSSL is doing.


Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded

More information about the openssl-users mailing list