Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Jsch dependency #28

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Jsch dependency #28

wants to merge 2 commits into from

Conversation

kakai248
Copy link

To fix #27.

I'm not really sure how to test this (or even how to build the plugin), so I would need some help on that. But the changes seemed straightforward to do them blind.

Let me know what do I need to do. Thanks!

@kakai248 kakai248 changed the title Update JGit and Jsch dependency Update Jsch dependency Aug 22, 2022
@sky-ricardocarrapico
Copy link

(sorry for the multiple accounts, but I have one personal and one for work)

I managed to test this and it seems to work. I had to disable signing and then published a version to mavenLocal. It can now clone my Git repository with the usual SSH settings that I have.

@sky-ricardocarrapico
Copy link

Actually, there's one more change that needs to be done because JGit does something that will end up with a NPE, as seen here: mwiede/jsch#43 (comment)

I'll push a commit with the change later today.

@neilmarietta
Copy link

Any news ? Should I better fork it ?

@melix
Copy link
Owner

melix commented Oct 13, 2022

I'm having hard times following if this PR fixes the pb or not :)

@sky-ricardocarrapico
Copy link

From my limited (only on our repo) amount of tests, it did indeed fix the issue.

@sky-ricardocarrapico
Copy link

Hey! Is there any way we can move forward with this? Something I should do?

@melix
Copy link
Owner

melix commented Nov 17, 2022

Yes, the only thing which is blocking me now is that I didn't have time to check that the fork of jsch which is used is legit (not some cryptomining stuff for ex). Would be nice to have some kind of evidence.

@sky-ricardocarrapico
Copy link

Totally fair. Since I'm also I third party here, I believe that is something you would only trust yourself to do. But if there's anything I can help with, please let me know.

Thank you!

@aSemy
Copy link

aSemy commented Dec 30, 2022

Yes, the only thing which is blocking me now is that I didn't have time to check that the fork of jsch which is used is legit (not some cryptomining stuff for ex). Would be nice to have some kind of evidence.

Hi 👋, I'm the author of the Gradle PR that swaps out the abandoned jsch lib with the maintained mweide jsch.

The discussion about legitimacy of the fork can be side stepped, because jsch isn't needed in newer versions of jgit (v6+), so if you updated jgit from v5 then this would improve support for newer ssh key types (which was the point of the upgrade).

There's more info in the Gradle PR:

@melix
Copy link
Owner

melix commented Jan 2, 2023

ahhh, sounds interesting, thanks for the hint!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Authentication problems using SSH
5 participants