Hi there,

JSch 0.1.37 has been released.
It is available at
  http://prdownloads.sourceforge.net/jsch/jsch-0.1.37.zip?download
and its md5sum is f798fbaaea9d912030992ee935398d1e
And you can get its byte code in jar file format at
  http://prdownloads.sourceforge.net/jsch/jsch-0.1.37.jar?download
and its md5sum is 84eced13821d9330a3e89ae769648dc9


Changes since version 0.1.36:
- bugfix: some sftpd will send invalid data in sftp protocol
          point of view, and we need to work around such data. FIXED.
- bugfix: the stream forwarding had been broken since 0.1.30.  FIXED.
- bugfix: failed to detect 'SSH_MSG_CHANNEL_OPEN_FAILURE'.     FIXED.
- bugfix: ChannelSftp will generate the unfavorable absolute pathname
          in some case.                                        FIXED.
- bugfix: failed to ignore the invalid public-key file.        FIXED.
- change: ignoring empty data sent by 'SSH_MSG_CHANNEL_DATA' and
           'SSH_MSG_CHANNEL_EXTENDED_DATA'.
- change: updating copyright messages; 2007 -> 2008
- change: build.xml will enable 'javac.debug' option by the default.
- change: added logging messages to IndentityFile and Session class.
- change: followings are deprecated methods,
           InputStream ChannelSftp#get(String src,
                                       int mode)
           InputStream ChannelSftp#get(String src,
                                       SftpProgressMonitor,
                                       int mode)
- feature: following method is added,
           InputStream ChannelSftp#get(String src,
                                       SftpProgressMonitor monitor,
                                       long skip)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users

Reply via email to