Skip to content

Latest commit

 

History

History
59 lines (38 loc) · 3.38 KB

CHANGES.md

File metadata and controls

59 lines (38 loc) · 3.38 KB

Planned for next version

Bug fixes

  • GH-268 (Regression in 2.9.0) Heartbeat should throw an exception if no reply arrives within the timeout.

  • GH-275 SFTP: be more lenient when reading SSH_FXP_STATUS replies.

  • GH-282 Correct setting file permissions on newly written host key files on Windows.

  • GH-283 Fix handling of CoreModuleProperties.PASSWORD_PROMPTS.

  • GH-285 Fix compilation failure on Java 19.

  • GH-293 Handle SFTP buffer sizes larger than the server limit better.

  • GH-294 Fix memory leak in SftpFileSystemProvider.

  • GH-297 Auto-configure file password provider for reading encrypted SSH keys.

  • GH-298 Server side heartbeat not working.

  • GH-300 Read the channel id in SSH_MSG_CHANNEL_OPEN_CONFIRMATION as unsigned int.

  • GH-313 Log exceptions in the SFTP subsystem before sending a failure status reply.

  • SSHD-1315 Do not log sensitive data at log level TRACE.

  • SSHD-1316 Possible OOM in ChannelPipedInputStream (fix channel window).

  • SSHD-1319 Use position in SftpRemotePathChannel.transferFrom().

Major code re-factoring

Potential compatibility issues

Minor code helpers

Behavioral changes and enhancements

  • CoreModuleProperties.PASSWORD_PROMPTS is now also used for password authentication. Previous versions used it only for keyboard-interactive authentication. The semantics has been clarified to be the equivalent of the OpenSSH configuration NumberOfPasswordPrompts, which is actually the number of authentication attempts. (In keyboard-interactive authentication, there may be several prompts per authentication attempt.) Only interactive authentication attempts using UserInteraction count towards the limit. Attempts fulfilled by explicitly provided passwords (via session.addPasswordIdentity() or session.setPasswordIdentityProvider()) are not counted. The default value of the property is unchanged and is 3, as in OpenSSH. The limit is applied independently for both authentication mechanisms: with the default setting, there can be three keyboard-interactive authentication attempts, plus three more password authentication attempts if both methods are configured and applicable.