• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ssh-plugin
    • None
    • jenkins-2.73.3
    • trilead-ssh2-build-217-jenkins-11

      SSH key type Ed25519 are not supported by TrileadSSH2Java_213

      Would be great to support it.

          [JENKINS-30319] SSH - Ed25519 keys not supported

          Phil Rumble added a comment -

          This would be great to have updated!!

           

          Can you see to it?

           

          Phil Rumble added a comment - This would be great to have updated!!   Can you see to it?  

          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.

          Peter Lieverdink added a comment - 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.

          This still appears to be an issue with Jenkins 2.73.3 using ssh plugin version 2.5.  ed25519 keys do not work and there is an error stating " Can't connect to server" when attempting to add a new ssh site in the Jenkins global configuration.  See the attached screenshot for refrence.

          Jenkins logs also show an error as follows.

          ERROR: Failed to authenticate with public key
          [[8mha:////4IzJAEUbJVXO0x7sOCoWD5u1OPX6pWxoNK4vpa0nY2K0AAAAVx+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0mV3NWzufebKBsTA0NFEYMUmgZnCA1SyAABjCCFBQC2xNaiYAAAAA==[[0mcom.jcraft.jsch.JSchException: invalid privatekey: [B@3802c10b

          The key is valid and works when using the ssh client on our jenkins server.

          Michael Watters added a comment - This still appears to be an issue with Jenkins 2.73.3 using ssh plugin version 2.5.  ed25519 keys do not work and there is an error stating " Can't connect to server" when attempting to add a new ssh site in the Jenkins global configuration.  See the attached screenshot for refrence. Jenkins logs also show an error as follows. ERROR: Failed to authenticate with public key [[8mha:////4IzJAEUbJVXO0x7sOCoWD5u1OPX6pWxoNK4vpa0nY2K0AAAAVx+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0mV3NWzufebKBsTA0NFEYMUmgZnCA1SyAABjCCFBQC2xNaiYAAAAA== [[0mcom.jcraft.jsch.JSchException: invalid privatekey: [B@3802c10b The key is valid and works when using the ssh client on our jenkins server.

          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.

          Dirk Heinrichs added a comment - 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.

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

          Michael Watters added a comment - Perhaps it would be nice to warn users that ed25519 keys are not supported.

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

          Dirk Heinrichs added a comment - Seems I was wrong with ecdsa keys. They also don't work.

          Do you know if https://github.com/jenkinsci/trilead-ssh2/pull/13 is supposed to fix this ?

          Benoit Guérout added a comment - Do you know if https://github.com/jenkinsci/trilead-ssh2/pull/13 is supposed to fix this ?

          Just added an ed_25519 public key to my profile on an up-to-date Jenkins LTS installation and got a warning: "‘ssh-ed25519’ does not look like a valid key type". Trying to access the CLI via SSH also failed with a "Permission denied (publickey)." error message from SSH.

          So why is this supposed to be fixed?

          Dirk Heinrichs added a comment - Just added an ed_25519 public key to my profile on an up-to-date Jenkins LTS installation and got a warning: "‘ssh-ed25519’ does not look like a valid key type". Trying to access the CLI via SSH also failed with a "Permission denied (publickey)." error message from SSH. So why is this supposed to be fixed?

          Björn Pedersen added a comment - For further keytypes to be recognized, the decoders from  https://github.com/apache/mina-sshd/tree/master/sshd-common/src/main/java/org/apache/sshd/common/config/keys/impl  need to be backported to https://github.com/jenkinsci/sshd-plugin/blob/master/src/main/java/org/jenkinsci/main/modules/cli/auth/ssh/PublicKeySignatureWriter.java  

          Reopend as the java-ssh to openssh conversion forn non DSS/RSA-keys is still missing

          Björn Pedersen added a comment - Reopend as the java-ssh to openssh conversion forn non DSS/RSA-keys is still missing

            Unassigned Unassigned
            beber Bertrand Jacquin
            Votes:
            13 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: