Re: [egit-dev] SSH: Switching from Jsch to Apache Mina

[Matthias Sohn <matthias.sohn@xxxxxxxxx>]

On Wed, Jan 24, 2018 at 10:57 AM, Konrad Windszus <konrad_w@xxxxxx> wrote:

Recently a lot of bugs have been discovered in Jsch (e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=529173 or https://bugs.eclipse.org/bugs/show_bug.cgi?id=526867). Although workarounds for those have been implemented there is still the open issue with supporting ssh-agent (https://bugs.eclipse.org/bugs/show_bug.cgi?id=179924).

Jsch seems to be quite dead since a year now (https://sourceforge.net/p/jsch/mailman/message/36187233/) therefore I am wondering whether it would be a good idea for JGit/EGit to switch to Apache Mina SSHD (https://mina.apache.org/sshd-project/) for the SSH authentication. Apache Mina SSH is quite active with the last release just 12 days ago (https://git-wip-us.apache.org/repos/asf?p=mina-sshd.git;a=summary).

Have you thought already in this direction?

I guess the Apache Mina SSHD license (ASF 2.0) shouldn't be a problem to integrate via Orbit, in fact an older version (0.0.7) is already provided (http://download.eclipse.org/tools/orbit/downloads/drops/R20170303204511/repository/plugins/org.apache.sshd.core_0.7.0.v201303101611.jar)

yes, I was also thinking in this direction. It seems the jsch maintainer disappeared and we even don't know where to find the jsch source code repository.

Moving to Mina would also imply that we need another integration to configure it in Eclipse Preferences. For Jsch we use the integration provided

by Eclipse platform. I guess this should then also be moved to Mina. We should ask that question on the cross-project-issues-dev mailing list to see if we can setup

a joined plan with the other Eclipse components relying on Jsch.

--Matthias