[stunnel-users] Premature socket closure - race condition bug?

Mon Sep 22 13:13:21 CEST 2014

Compiled and installed on the Linux Mint server and looking fine so far 
using my test example. If nothing shows up in the next few hours of normal 
running it should be fine.

It's of lower priority, but I'd like to update the client machines as well 
when the release goes official. This may be better in a separate thread, or 
already exist in an FAQ I've not found, but
as I have about 50 (currently, eventually >80) sites to update (mostly 
Windows 7, some XPSP3), is there a way for the Windows install to be run 
unattended? Failing that, is there a list, or way to generate a list, of 
updated binaries + reg/config entries so I can make myself an unattended 
install/upgrade? Most sites are currently on 5.01, but some are still on 
4.56.

-----Original Message----- 
From: Michal Trojnara
Sent: Monday, September 22, 2014 11:00 AM
To: stunnel-users at stunnel.org
Subject: Re: [stunnel-users] Premature socket closure - race condition bug?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Graham Nayler wrote:
> In the failure scenario though, the returned status was
> (POLLIN|POLLHUP).

Great work.  I indeed forgot that the POLLHUP condition may be set
while some buffered data is still available.

Could you try:
https://www.stunnel.org/downloads/beta/stunnel-5.05b1.tar.gz
?

Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlQf80IACgkQ/NU+nXTHMtG3pACfeYvvrabt8TAM7CsOP1fm9nod
/0UAoPpF7W5FkGjzb1u3E+6ZRHtoyi2L
=p6UY
-----END PGP SIGNATURE-----
_______________________________________________
stunnel-users mailing list
stunnel-users at stunnel.org
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users 