Re: [egit-dev] [jgit-dev] Bug 520927: moving away from JSch

[Thomas Wolf <thomas.wolf@xxxxxxxxxx>]

> On 18 Nov 2018, at 22:05 , Randall S. Becker <rsbecker@xxxxxxxxxxxxx> wrote:
> 
> A key operability requirement, as you mentioned, is not asking for passwords
> repeatedly. This problem showed up for passphrases when host case
> sensitivity showed up on ~/.ssh/config. This was fixed. However, the
> prompting for passphrases should be included. A mechanism for sharing
> authentication is important for operability within EGit so that users of
> JGit who add a separate plugin from EGit can avoid reprompting. I suggest
> that this be made available. It was in JSch and would be a real pain not to
> have that capability going forward.

I only understand half of this. The JGit CredentialsProvider is still available,
and still works in exactly the same ways. The Apache MINA sshd implementation
is hooked up such that the CredentialsProvider from JGit _is_ used.

A mechanism similar to what happened in JSch _has_ been made available.
JSch caches keys on the JSch instance; the new Apache MINA sshd implementation
gives you the possibility to provide a KeyCache to the SshdSessionFactory to get
similar behavior.

If you have similar requirements as EGit and want to use some kind of secure store,
the EGit implementation can serve as a model. AFAIK JSch did not include such
functionality either. It just avoided multiple password prompts because it cached keys
under the hood.

Maybe you just give the new implementation a try?

Cheers,

  Thomas