Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-21756

Improve logging of JSch library

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • fuse-7.13-GA
    • fuse-7.12-GA
    • Camel
    • None
    • Very Likely

      When diagnosing a disconnection issue between Camel SFTP component and an SFTP server, and after setting the JSch log to TRACE level, we see the following log output:

      JSCH -> kex: server: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,rsa1024-sha1
      JSCH -> kex: server: ssh-rsa,ssh-dss
      JSCH -> kex: server: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-ctr,blowfish-cbc,cast128-cbc,arcfour256,arcfour128,3des-ctr,3des-cbc
      JSCH -> kex: server: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-ctr,blowfish-cbc,cast128-cbc,arcfour256,arcfour128,3des-ctr,3des-cbc
      JSCH -> kex: server: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,umac-64@openssh.com
      JSCH -> kex: server: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,umac-64@openssh.com
      JSCH -> kex: server: zlib@openssh.com,zlib,none
      JSCH -> kex: server: zlib@openssh.com,zlib,none
      JSCH -> kex: server: 
      JSCH -> kex: server: 
      JSCH -> kex: client: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
      JSCH -> kex: client: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160
      JSCH -> kex: client: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
      JSCH -> kex: client: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
      JSCH -> kex: client: hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
      JSCH -> kex: client: hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
      JSCH -> kex: client: none
      JSCH -> kex: client: none
      JSCH -> kex: client: 
      JSCH -> kex: client: 
      JSCH -> Disconnecting from sftp.myserver.com port 2222 

       

      About these log entries, I have the following remarks:

      • We do not know why the disconnection happened
      • We see the entries "kex: server" repeat several times, with different ciphers, but that is not clear what is the final cipher list which will be presented to the other connection participant. The same goes for "kex:client"

       

      Could the TRACE logging of this JSch library be improved? It is very painful to diagnose these issues with the log entries like that.

            ldemasi Luigi De Masi
            rhn-support-anarvaez Alfredo Narvaez
            Tomas Veskrna Tomas Veskrna
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: