Subject: Re: Keepalive timeout with dropbear client
Hi David,
Dropbear since 2015.68 always sets the socket non-blocking [1], so I think that
change should be safe on older versions. The only risk I can think of is if it
gets in some state where it might spin with 100% CPU.
Cheers,
Matt
[1]
https
Hi David,
Dropbear since 2015.68 always sets the socket non-blocking [1], so I think that
change should be safe on older versions. The only risk I can think of is if it
gets in some state where it might spin with 100% CPU.
Cheers,
Matt
[1]
https://secure.ucc.asn.au/hg/dropbear/annotate/10f198
Hi everyone,
We have been using version 65 of Dropbear to maintain an ssh connection to a
central server. It usually works fine, but when there is a network failure the
Dropbear client waits until there is a tcp timeout before declaring that there
was a keepalive timeout. So in practice even th
