Mercurial > dropbear
diff CHANGES @ 989:73ea0dce9a57 pam
Merge up to date
author | Matt Johnston <matt@ucc.asn.au> |
---|---|
date | Fri, 23 Jan 2015 21:38:47 +0800 |
parents | 735511a4c761 |
children | d63b569a7c86 |
line wrap: on
line diff
--- a/CHANGES Wed Mar 12 23:40:02 2014 +0800 +++ b/CHANGES Fri Jan 23 21:38:47 2015 +0800 @@ -1,3 +1,61 @@ +2014.66 - Thursday 23 October 2014 + +- Use the same keepalive handling behaviour as OpenSSH. This will work better + with some SSH implementations that have different behaviour with unknown + message types. + +- Don't reply with SSH_MSG_UNIMPLEMENTED when we receive a reply to our own + keepalive message + +- Set $SSH_CLIENT to keep bash happy, patch from Ryan Cleere + +- Fix wtmp which broke since 2013.62, patch from Whoopie + +2014.65 - Friday 8 August 2014 + +- Fix 2014.64 regression, server session hang on exit with scp (and probably + others), thanks to NiLuJe for tracking it down + +- Fix 2014.64 regression, clock_gettime() error handling which broke on older + Linux kernels, reported by NiLuJe + +- Fix 2014.64 regression, writev() could occassionally fail with EAGAIN which + wasn't caught + +- Avoid error message when trying to set QoS on proxycommand or multihop pipes + +- Use /usr/bin/xauth, thanks to Mike Frysinger + +- Don't exit the client if the local user entry can't be found, thanks to iquaba + +2014.64 - Sunday 27 July 2014 + +- Fix compiling with ECDSA and DSS disabled + +- Don't exit abruptly if too many outgoing packets are queued for writev(). Patch + thanks to Ronny Meeus + +- The -K keepalive option now behaves more like OpenSSH's "ServerAliveInterval". + If no response is received after 3 keepalives then the session is terminated. This + will close connections faster than waiting for a TCP timeout. + +- Rework TCP priority setting. New settings are + if (connecting || ptys || x11) tos = LOWDELAY + else if (tcp_forwards) tos = 0 + else tos = BULK + Thanks to Catalin Patulea for the suggestion. + +- Improve handling of many concurrent new TCP forwarded connections, should now + be able to handle as many as MAX_CHANNELS. Thanks to Eduardo Silva for reporting + and investigating it. + +- Make sure that exit messages from the client are printed, regression in 2013.57 + +- Use monotonic clock where available, timeouts won't be affected by system time + changes + +- Add -V for version + 2014.63 - Wednesday 19 February 2014 - Fix ~. to terminate a client interactive session after waking a laptop