4 Replies Latest reply on Jul 25, 2013 6:28 AM by Peter Krutý

    FTP Voyager authentication Problem ...

    cmartin67

      Users transfer date to serv-U server with FTP Voyager.

      User do also transfer data to some linux SFTP servers.

       

      We used to have FTP Voyager 15.2.0.15 - everything worked fine.

      Since updating to FTP Voyager 16.0.2.0 authentication
      with linux SFTP servers fail (connection to Serv-U is still working) It seames that the password is not transferred to the server.

       

      Whithout configuring user and password in server profile: I've been asked for a username - not for the password.

           Log: SSH_MSG_USERAUTH_FAILURE

       

           /var/log/messages:

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: Connection from 10.142.40.230 port 2087

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Client protocol version 2.0; client software version FTP Voyager_16.0.2.0

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: no match: FTP Voyager_16.0.2.0

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Enabling compatibility mode for protocol 2.0

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Local version string SSH-2.0-OpenSSH_5.1

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: user zfs-sftp matched group list sftponly at line 143

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: initializing for "zfs-sftp"

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_RHOST to "10.142.40.230"

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_TTY to "ssh"

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: do_cleanup

      Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: cleanup

       

      Anyone an idea what's wrong ?

      Thank you very much

       

      Christof

        • Re: FTP Voyager authentication Problem ...
          jonathan at solarwinds

          What does the FTP Voyager log look like?

            • Re: FTP Voyager authentication Problem ...
              cmartin67

              Log is like that:

               

              STATUS> Connecting to "10.140.1.4" on port 22.
              STATUS> Connected to 10.140.1.4:22 from 10.142.40.230:39144.
              STATUS> Negotiating SSH2 session with server...
              STATUS> Client Identification: SSH-2.0-FTP Voyager_16.0.2.0
              STATUS> Server Identification: SSH-2.0-OpenSSH_6.1
              STATUS> Initializing key exchange process...
              STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
              STATUS> Host Key Fingerprint: 70:52:3C:DF:43:19:6B:A9:77:DF:86:B1:82:0D:B7:D4
              STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: none
              STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: none
              STATUS> Selected public key protocol: ssh-rsa
              STATUS> Key exchange process successfully completed.
              COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
              SSH_MSG_SERVICE_ACCEPT: service accepted
              STATUS> Querying server for supported authentication methods
              COMMAND> SSH_MSG_USERAUTH_REQUEST: user: zfs-sftp; service: ssh-connection; type: none
              -------------
              /etc/issue.net
              -------------

              SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: keyboard-interactive
              STATUS> Supported authentication methods: keyboard-interactive
              ERROR> SSH Disconnect Error: no more authentication methods available.
              ERROR> Unable to login.
              ERROR> Connection attempt failed.  Retrying in 3 seconds...
              COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
              ERROR> The server has unexpectedly closed the connection.
              ERROR> Connection attempt failed.  Retrying in 3 seconds...

                • Re: FTP Voyager authentication Problem ...
                  Peter Krutý

                  Hi cmartin67,

                  let me check with our Dev team.

                  Thanks,

                  Peter

                  • Re: FTP Voyager authentication Problem ...
                    Peter Krutý

                    Hi cmartin67,

                     

                    I consulted this with Dev and it says in the log, your only available auth-method is keyboard-interactive.

                    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: keyboard-interactive

                    STATUS> Supported authentication methods: keyboard-interactive

                    Version 15 faked support for this type (what is violating RFC specification) and this was changed in v16 to behave according standard. So this may look like a bug, but it's actually a fix. However we decided to revert that behaviour in future versions, so in future releases you may expect the same behavior as for the version 15.

                     

                    Peter