[JIRA] [ssh-plugin] (JENKINS-30319) SSH - Ed25519 keys not supported

12 views
Skip to first unread message

bertrand@jacquin.bzh (JIRA)

unread,
Sep 5, 2015, 4:11:03 PM9/5/15
to jenkinsc...@googlegroups.com
Bertrand Jacquin created an issue
 
Jenkins / Bug JENKINS-30319
SSH - Ed25519 keys not supported
Issue Type: Bug Bug
Assignee: Unassigned
Components: ssh-plugin
Created: 05/Sep/15 8:10 PM
Environment: jenkins-1.609.3
Priority: Minor Minor
Reporter: Bertrand Jacquin

SSH key type Ed25519 are not supported by TrileadSSH2Java_213

Would be great to support it.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

moog621@gmail.com (JIRA)

unread,
Dec 22, 2016, 2:57:02 PM12/22/16
to jenkinsc...@googlegroups.com
Robert Moog commented on Bug JENKINS-30319
 
Re: SSH - Ed25519 keys not supported

I just bumped into this today when adding a slave node. Seriously, it's been over a year and Jenkins doesn't even support ECDSA.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

dothebart@citadel.org (JIRA)

unread,
Mar 3, 2017, 11:24:01 AM3/3/17
to jenkinsc...@googlegroups.com

since connectbot seems to support this nowadays (same client lib?)
https://github.com/connectbot/connectbot/issues/69 ; https://github.com/connectbot/sshlib/pull/26/files
shouldn't this just be an upgrade of the libraries?

philrumble@hotmail.com (JIRA)

unread,
Mar 21, 2017, 1:47:01 AM3/21/17
to jenkinsc...@googlegroups.com

This would be great to have updated!!

 

Can you see to it?

 

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

me@cafuego.net (JIRA)

unread,
Mar 21, 2017, 6:33:02 PM3/21/17
to jenkinsc...@googlegroups.com

The same goes for other key algorithms.

Or rather, not supporting them is one thing, but showing two pages of stack trace when a user enters one is another thing altogether.

Basic input validation would allow a user to see they entered an unsupported key type without being presented with a stack trace.

dirk.heinrichs@recommind.com (JIRA)

unread,
Dec 22, 2018, 8:00:03 AM12/22/18
to jenkinsc...@googlegroups.com

It's still the same in 2.150.1. However, I realize it's a feature (or lack thereof) of the underlying JSCH lib, which doesn't support it either. It only supports ecdsa.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

wattersm@watters.ws (JIRA)

unread,
Dec 26, 2018, 12:10:03 PM12/26/18
to jenkinsc...@googlegroups.com

Perhaps it would be nice to warn users that ed25519 keys are not supported.

dirk.heinrichs@recommind.com (JIRA)

unread,
Jan 5, 2019, 6:25:03 AM1/5/19
to jenkinsc...@googlegroups.com

Seems I was wrong with ecdsa keys. They also don't work.

bguerout@gmail.com (JIRA)

unread,
Jan 17, 2019, 3:50:02 PM1/17/19
to jenkinsc...@googlegroups.com

kuisathaverat@gmail.com (JIRA)

unread,
Jul 15, 2019, 4:52:04 AM7/15/19
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo resolved as Fixed
 
Change By: Ivan Fernandez Calvo
Status: Open Resolved
Resolution: Fixed
Released As: trilead-ssh2-build-217-jenkins-11
Reply all
Reply to author
Forward
0 new messages