[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [Libevent-users] Closing SSL sessions
- To: libevent-users@xxxxxxxxxxxxx
- Subject: Re: [Libevent-users] Closing SSL sessions
- From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
- Date: Thu, 2 Aug 2018 03:10:26 +0300
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Wed, 01 Aug 2018 20:10:32 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=h75KX/G22sNQHWTACL6lzdpn2Vn1wnvKHNLERT+e2vw=; b=XoO7yVOeTrv4UPONjihMYyqcKGiv6JqbjdA3HbVAtT3QRdI1WckNLYcAWLfMZUOTAz dyEWfqfCUKUJti+OIU073I2o2ET6VAAswsnubPQTiCblbP4rhDarBn+1HMM4x/NKVMk0 1/CRz3RDObEkAsN+1g3AIPIq5tv/DAbJjwhpYe1TLDUizNygJS17Dwu8+gCRqvCh84fG a1ovqHMZkLhMZgeHcCn2luIwJcAFvVWFgMWUMIkR9panAhGlWLZlSVnDvVy9RdmMh7qx e+Km+f97faHnoXBA9filmDiuz6fqdVKCMRKNKk2F3i2Elv8OqlZA6W+TZylIDs9ebmIW S0Xg==
- In-reply-to: <73313A38-495A-4145-ABED-A303FFE29065@redfish-solutions.com>
- References: <73313A38-495A-4145-ABED-A303FFE29065@redfish-solutions.com>
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
- User-agent: NeoMutt/20180716
On Thu, Jul 05, 2018 at 06:40:10PM -0600, Philip Prindeville wrote:
> http://www.wangafu.net/~nickm/libevent-book/Ref6a_advanced_bufferevents.html
>
> "Currently the only workaround is to do lazy SSL shutdowns manually. While this breaks the TLS RFC, it will make sure that sessions will stay in cache once closed. The following code implements this workaround.”
>
> Is this still the case? I was hoping that libevent had gotten updated and the book was lagging behind...
Looks like it is, since there is no SSL_shutdown() around.
AFAIR I tried to add it, but it is not that simple since SSL_shutdown()
generates IO ("close notify"), while once we are ready to close the
socket we are not expecting this.
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.