Community
Participate
Working Groups
Apache MINA sshd has a sshd-putty component for reading PuTTY key files. Include it in Orbit (CQs...) and then use it in the JGit Apache MINA sshd ssh client. Should be as simple as registering the key readers in addition to the existing ones.
This will have to wait until either: * Platform also moves to sshd 2.0.0 and includes sshd-contrib and sshd-scp in Orbit, or * we move to sshd >= 2.1.0 and include sshd-putty in Orbit The separate sshd-putty artifact exists only since 2.1.0; before it was in sshd-contrib, where other code has a dependency on sshd-scp.
Filed CQ for sshd-putty 2.2.0 https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20150 for JGit and https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20151 for Orbit
CQ 20150 is in state "awaiting_committer". Shouldn't it be returned to the IP Team after the artifacts have been attached? Or does that happen when it's +1'ed by Chris (PMC)?
missed to forward the CQ to the IP team, did this now
New Gerrit change created: https://git.eclipse.org/r/145187
New Gerrit change created: https://git.eclipse.org/r/146758
New Gerrit change created: https://git.eclipse.org/r/146760
Turns out we cannot do this inside the ssh.apache library in JGit; it'd force the putty dependency on all clients. Doing it for EGit only in the EGitSshdSessionFactory would be possible, but there's no user request for it. Doing it only in EGit might require setting up a unit test infrastructure for this feature in EGit. Or test the feature in JGit even though it'd be implemented in EGit. So for now we drop this, also due to capacity constraints. If it should ever be needed, [1] shows what would have to be done. Some tests in JGit also exist in [2]. [1] https://git.eclipse.org/r/#/c/146760/1/org.eclipse.egit.core/src/org/eclipse/egit/core/internal/EGitSshdSessionFactory.java [2] https://git.eclipse.org/r/#/c/146758/