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

too old sshd version for actual Jenkins LTS usage #1254

Closed
waffel opened this issue Aug 9, 2017 · 6 comments · Fixed by #1322
Closed

too old sshd version for actual Jenkins LTS usage #1254

waffel opened this issue Aug 9, 2017 · 6 comments · Fixed by #1322
Milestone

Comments

@waffel
Copy link

waffel commented Aug 9, 2017

The used version of the Apache sshd service 1.0.0 seems to be too old to use GitBlit with the latest Jenkins LTS version 2.60.2.

The issue is reported to Jenkins too: https://issues.jenkins-ci.org/browse/JENKINS-45769

A simple "replacement" of the sshd jar files seems to not work because of resulting ClassNotFoundExceptions.

Possible a new version of gitblit can provide a actual sshd version 1.6.0 from the apache project to solve this problem.

We have seen this problem with gitblit 1.8.0 running under a recent JDK8 in a tomcat 8 container as WAR application.

A "native" git implementation still works ... only the new trilead java implementation seems to require a more recent ssh key negotiation.

@j123b567
Copy link
Contributor

Did you try to simply generate new pair of keys using e.g. rsa? You are using legacy DSA/ssh-dss algorithm which is not supported in recent SSH implementations and will not be supported in the future by much more software. This seems not to be a bug of jenkins nor gitblit but security feature of recent SSH implementations.

@rpardini
Copy link

rpardini commented Jan 3, 2018

#1272 fixes this.

@flaix
Copy link
Member

flaix commented Sep 13, 2018

Is this a persisting problem? I have Jenkins 1.121.2 running, and I have a freestyle project clongin with a RSA SSH key from the current Gitblit without problems.

@waffel
Copy link
Author

waffel commented Oct 5, 2018

Please close this issue. It seems to be fixed.

@waffel waffel closed this as completed Oct 5, 2018
@rpardini
Copy link

@waffel fixed where? #1272 (disclosure: my patch) is the only known way to fix this. There have been no commits to this gitblit repo since 2017. Wonder where you got the idea this was fixed, I'd love to get back to pristine upstream.

@flaix flaix added this to the 1.9.0 milestone Nov 9, 2019
@flaix
Copy link
Member

flaix commented Nov 9, 2019

I also think that this particular problem mentioned in the Jenkins issue would be fixed by creating a ssh-rsa key for the GitBlit server. I wonder why none was created by GitBlit.
The SSHD update is part of the next version, albeit only to 1.2.0.

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 a pull request may close this issue.

4 participants