On Sat, 04 Jun 2022 14:54:12 +0200, Axel Beckert wrote:

> I also checked what close() returns. It is actually "undef". Also
> IO::Socket::SSL does not document any return value for close(). So the
> return code is actually not meant to mean anything.

Thanks for investigating this further!
 
> Additionally the POD also states on close():
> 
>   The default behavior is thus to only send a close notify but not
>   wait for the close notify of the peer. If this is required
>   "SSL_fast_shutdown" need to be explicitly set to false.
> 
> So it also does have nothing on which a success or failure could be
> determined.
> 
> So IMHO we can and should just drop that "or die()".

Full ack.
 
> Will do 

Thanks for adding the fix and uploading!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   

Attachment: signature.asc
Description: Digital Signature

Reply via email to