Fork of JSch-0.1.55

See original README

Why should you use this library?

As I explained in a blog post the main points are:

• OpenSSH has disabled ssh-rsa in release 8.8 per default and you need a library which supports rsa-sha2-256 and rsa-sha2-512.
• Drop in replacement: just change dependency coordinates and you are good to go.
• No active maintenance of JSch at SourceForge.
• Stay in sync with OpenJDK features so there is no need for additional dependencies.

Is there any documentation?

Not much. Check the example code in the examples folder. And there are some wiki pages, i.e. Jsch-Configuration and Jsch-Logging.

Versioning

Up until 0.2.26 the versioning followed the original jsch scheme, from 2.27.0 on, we switched to semantic versioning, expressing that the library api is stable and used in production.

How to use this library as a replacement for com.jcraft:jsch

Make sure, that you only have one jsch dependency on your classpath. For example you can check the output of mvn dependency:tree.

by replacing a direct maven dependency

replace

<dependency>
    <groupId>com.jcraft</groupId>
    <artifactId>jsch</artifactId>
    <version>0.1.55</version>
</dependency>

with

<dependency>
  <groupId>com.github.mwiede</groupId>
  <artifactId>jsch</artifactId>
  <version>2.28.0</version>
</dependency>

by replacing jsch as a transitive maven dependency

When you have an artifact foo:bar, which contains com.jcraft:jsch as a transitive dependency, you need to add com.github.mwiede:jsch as another dependency and exclude the jcraft one:

<dependency>
  <groupId>com.github.mwiede</groupId>
  <artifactId>jsch</artifactId>
  <version>2.28.0</version>
</dependency>
<dependency>
  <groupId>foo</groupId>
  <artifactId>bar</artifactId>
  <exclusions>
        <exclusion>  
          <groupId>com.jcraft</groupId>
          <artifactId>jsch</artifactId>
        </exclusion>
      </exclusions> 
</dependency>

Addition: You can further exclude any of com.jcraft:jsch.agentproxy.jsch, com.jcraft:jsch.agentproxy.core or com.jcraft:jsch.agentproxy.pageant, because these modules where integrated in this fork (see release notes of 0.1.66).

FAQ

Which is the minimum Java version required?

• Java 8. For more limitations, see next answer.

Are ssh-ed25519, ssh-ed448, curve25519-sha256, curve448-sha512 & chacha20-poly1305@openssh.com supported?

• This library is a Multi-Release-jar, which means that you can only use certain features when a more recent Java version is used.
  • In order to use ssh-ed25519 & ssh-ed448, you must use at least Java 15 or add Bouncy Castle (bcprov-jdk18on) to the classpath.
  • In order to use curve25519-sha256 & curve448-sha512, you must use at least Java 11 or add Bouncy Castle (bcprov-jdk18on) to the classpath.
  • In order to use chacha20-poly1305@openssh.com, you must add Bouncy Castle (bcprov-jdk18on) to the classpath.
• As of the 0.1.66 release, these algorithms can now be used with older Java releases if Bouncy Castle (bcprov-jdk18on) is added to the classpath.
  • As of the 0.1.72 release, chacha20-poly1305@openssh.com can only be used if Bouncy Castle (bcprov-jdk18on) is added to the classpath.

Why do ssh-rsa type keys not work with this JSch fork and my server?

• As of the 0.2.0 release, the RSA/SHA1 signature algorithm is disabled by default.
  • SHA1 is no longer considered secure by the general cryptographic community and this JSch fork strives to maintain secure choices for default algorithms that it will utilize.
  • This also follows the lead of the OpenSSH project in which they disabled RSA/SHA1 signatures by default as of OpenSSH release 8.8.
• ssh-rsa type keys continue to function by default with the RSA/SHA256 (rsa-sha2-256) & RSA/SHA512 (rsa-sha2-512) signature algorithms defined by RFC 8332.
• If your server only supports RSA/SHA1 signatures and you require their use in your application, then you will need to manually reenable them by one of the following means (also see wiki page Jsch-Configuration):
  • Globally by adding "ssh-rsa" to the jsch.server_host_key + jsch.client_pubkey properties.
  • Globally by executing something similar to JSch.setConfig("server_host_key", JSch.getConfig("server_host_key") + ",ssh-rsa") + JSch.setConfig("PubkeyAcceptedAlgorithms", JSch.getConfig("PubkeyAcceptedAlgorithms") + ",ssh-rsa").
  • On a per-session basis by executing something similar to session.setConfig("server_host_key", session.getConfig("server_host_key") + ",ssh-rsa") + session.setConfig("PubkeyAcceptedAlgorithms", session.getConfig("PubkeyAcceptedAlgorithms") + ",ssh-rsa").

Is this fork 100% compatible with original JSch, because the connection to my server does not work any more!

• For compatibility with OpenSSH and improved security, the order of crypto algorithms was changed. If you still want to use older or deprecated algorithms, you need to change the configuration. Examples see #37, #40
• To make it easier to adjust the crypto algorithms, starting with 0.1.65 the following system properties can be set at your application's startup:
  • jsch.kex
    • analogous to JSch.setConfig("kex", "...")
  • jsch.server_host_key
    • analogous to JSch.setConfig("server_host_key", "...")
  • jsch.prefer_known_host_key_types
    • analogous to JSch.setConfig("prefer_known_host_key_types", "...")
  • jsch.enable_server_sig_algs
    • analogous to JSch.setConfig("enable_server_sig_algs", "...")
  • jsch.cipher

Other Projects Using JSch

• Jsync https://github.com/fizzed/jsync - Provides a simple, efficient, reliable, and pure Java rsync-like file and directory synchronization tool that can be used programmatically.
• Blaze https://github.com/fizzed/blaze - A way to run Java files as scripts, with powerful SSH, SFTP, and rsync-like features built right in.

Changes since fork:

See ChangeLog.md