GNU bug report logs - #49449
28: TLS connection never gets to "open" stage

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mattias Engdegård <mattiase <at> acm.org>
Cc: 49449 <at> debbugs.gnu.org, larsi <at> gnus.org
Subject: bug#49449: 28: TLS connection never gets to "open" stage
Date: Sat, 10 Jul 2021 22:31:25 +0300

> From: Mattias Engdegård <mattiase <at> acm.org>
> Date: Sat, 10 Jul 2021 21:22:09 +0200
> Cc: larsi <at> gnus.org, 49449 <at> debbugs.gnu.org
> 
> 10 juli 2021 kl. 20.54 skrev Eli Zaretskii <eliz <at> gnu.org>:
> 
> > The busy-wait loop can delay the sentinel call, but do you understand
> > why the sentinel isn't called once the loop is over?
> 
> Sort of; see previous discussion. In short: once the busy-wait loop is over, the TLS handshake succeeds immediately (because sufficient time has passed) but the logic isn't set up for this path and enters a state where the sentinel cannot be called.

That's my question: why cannot the sentinel be called in this case?
what prevents it from being called?  Apologies if I missed the
explanation, and could you please repeat it?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.