Windows is connected to linux, and the command line terminal can be connected. Why cannot the file transfer terminal be connected?

Source: Internet
Author: User
Tags hmac
Windows is connected to linux, and the command line terminal can be connected. Why cannot the file transfer terminal be connected? -- Linux general technology-Linux technology and application information. For details, refer to the following section. Windows is connected to linux, and the command line terminal can be connected. Why cannot the file transfer terminal be connected?
The secureFX log is as follows:
I SSH2Core version 6.1.0.423
I Connecting to 222.141.118.117: 22...
I Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
I Using protocol SSH2
I RECV: Remote Identifier = "SSH-2.0-OpenSSH_4.3"
I CAP: Remote can re-key
I CAP: Remote sends language in password change requests
I CAP: Remote sends algorithm name in PK_ OK packets
I CAP: Remote sends algorithm name in public key packets
I CAP: Remote sends algorithm name in signatures
I CAP: Remote sends error text in open failure packets
I CAP: Remote sends name in service accept packets
I CAP: Remote clients des port number in x11 open packets
I CAP: Remote uses 160 bit keys for SHA1 MAC
I CAP: Remote supports new diffie-hellman group exchange messages
I CAP: Remote correctly handles unknown SFTP extensions
I CAP: Remote correctly encodes OID for gssapi
I CAP: Remote correctly uses connected addresses in forwarded-tcpip requests
I CAP: Remote can do SFTP version 4
I CAP: Remote x.509v3 uses ASN.1 encoding for DSA signatures
I GSS: Requesting full delegation
I GSS: [Kerberos] SPNs: host@222.141.118.117
I GSS: [Kerberos] Disabling gss mechanic
I GSS: [Kerberos] InitializeSecurityContext () failed.
I GSS: [Kerberos] security package does not have any available creden
I The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-group1-sha1-toWM5Slw5Ew8Mqkay + al2g =
I GSS: Requesting full delegation
I GSS: [Kerberos w/Group Exchange] SPNs: host@222.141.118.117
I GSS: [Kerberos w/Group Exchange] Disabling gss mechanic
I GSS: [Kerberos w/Group Exchange] InitializeSecurityContext () failed.
I GSS: [Kerberos w/Group Exchange] No creden are available in the security package.
I The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay + al2g =
I SEND: KEXINIT
I RECV: Read kexinit
I Available Remote Kex Methods = diffie-hellman-group-exchange-sha1, diffie-hellman-group1-sha1
I Selected Kex Method = diffie-hellman-group-exchange-sha1
I Available Remote Host Key Algos = ssh-rsa, ssh-dss
I Selected Host Key Algo = ssh-dss
I Available Remote Send Ciphers = aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc, arcfour, aes192-cbc, aes256-cbc, rijndael-cbc@lysator.liu.se
I Selected Send Cipher = aes256-cbc
I Available Remote Recv Ciphers = aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc, arcfour, aes192-cbc, aes256-cbc, rijndael-cbc@lysator.liu.se
I Selected Recv Cipher = aes256-cbc
I Available Remote Send Macs = hmac-md5, hmac-sha1, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1-96, hmac-md5-96
I Selected Send Mac = hmac-sha1
I Available Remote Recv Macs = hmac-md5, hmac-sha1, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1-96, hmac-md5-96
I Selected Recv Mac = hmac-sha1
I Available Remote Compressors = none, zlib
I Selected Compressor = none
I Available Remote Decompressors = none, zlib
I Selected Decompressor = none
I Changing state from STATE_EXPECT_KEX_INIT to STATE_KEY_EXCHANGE
I SEND: KEXDH_GEX_REQUEST
I RECV: KEXDH_GEX_GROUP
I SEND: KEXDH_INIT
I RECV: KEXDH_REPLY
I SEND: NEWKEYS
I Changing state from STATE_KEY_EXCHANGE to STATE_EXPECT_NEWKEYS
I RECV: NEWKEYS
I Changing state from STATE_EXPECT_NEWKEYS to STATE_CONNECTION
I SEND: SERVICE_REQUEST [ssh-userauth]
I RECV: SERVICE_ACCEPT [ssh-userauth] -- OK
I SENT: USERAUTH_REQUEST [none]
I RECV: USERAUTH_FAILURE, continuations [publickey, password, keyboard-interactive]
I SENT: USERAUTH_REQUEST [password]
I RECV: AUTH_SUCCESS
I SEND [0]: SSH_MSG_CHANNEL_EOF
I SSH2Core version 6.1.0.423
I Connecting to 222.141.118.117: 22...
I Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
I Using protocol SSH2
I RECV: Remote Identifier = "SSH-2.0-OpenSSH_4.3"
I CAP: Remote can re-key
I CAP: Remote sends language in password change requests
I CAP: Remote sends algorithm name in PK_ OK packets
I CAP: Remote sends algorithm name in public key packets
I CAP: Remote sends algorithm name in signatures
I CAP: Remote sends error text in open failure packets
I CAP: Remote sends name in service accept packets
I CAP: Remote clients des port number in x11 open packets
I CAP: Remote uses 160 bit keys for SHA1 MAC
I CAP: Remote supports new diffie-hellman group exchange messages
I CAP: Remote correctly handles unknown SFTP extensions
I CAP: Remote correctly encodes OID for gssapi
I CAP: Remote correctly uses connected addresses in forwarded-tcpip requests
I CAP: Remote can do SFTP version 4
I CAP: Remote x.509v3 uses ASN.1 encoding for DSA signatures
I GSS: Requesting full delegation
I GSS: [Kerberos] SPNs: host@222.141.118.117
I GSS: [Kerberos] Disabling gss mechanic
I GSS: [Kerberos] InitializeSecurityContext () failed.
I GSS: [Kerberos] security package does not have any available creden
I The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-group1-sha1-toWM5Slw5Ew8Mqkay + al2g =
I GSS: Requesting full delegation
I GSS: [Kerberos w/Group Exchange] SPNs: host@222.141.118.117
I GSS: [Kerberos w/Group Exchange] Disabling gss mechanic
I GSS: [Kerberos w/Group Exchange] InitializeSecurityContext () failed.
I GSS: [Kerberos w/Group Exchange] No creden are available in the security package.
I The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay + al2g =
I SEND: KEXINIT
I RECV: Read kexinit
I Available Remote Kex Methods = diffie-hellman-group-exchange-sha1, diffie-hellman-group1-sha1
I Selected Kex Method = diffie-hellman-group-exchange-sha1
I Available Remote Host Key Algos = ssh-rsa, ssh-dss
I Selected Host Key Algo = ssh-dss
I Available Remote Send Ciphers = aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc, arcfour, aes192-cbc, aes256-cbc, rijndael-cbc@lysator.liu.se
I Selected Send Cipher = aes256-cbc
I Available Remote Recv Ciphers = aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc, arcfour, aes192-cbc, aes256-cbc, rijndael-cbc@lysator.liu.se
I Selected Recv Cipher = aes256-cbc
I Available Remote Send Macs = hmac-md5, hmac-sha1, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1-96, hmac-md5-96
I Selected Send Mac = hmac-sha1
I Available Remote Recv Macs = hmac-md5, hmac-sha1, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1-96, hmac-md5-96
I Selected Recv Mac = hmac-sha1
I Available Remote Compressors = none, zlib
I Selected Compressor = none
I Available Remote Decompressors = none, zlib
I Selected Decompressor = none
I Changing state from STATE_EXPECT_KEX_INIT to STATE_KEY_EXCHANGE
I SEND: KEXDH_GEX_REQUEST
I RECV: KEXDH_GEX_GROUP
I SEND: KEXDH_INIT
I RECV: KEXDH_REPLY
I SEND: NEWKEYS
I Changing state from STATE_KEY_EXCHANGE to STATE_EXPECT_NEWKEYS
I RECV: NEWKEYS
I Changing state from STATE_EXPECT_NEWKEYS to STATE_CONNECTION
I SEND: SERVICE_REQUEST [ssh-userauth]
I RECV: SERVICE_ACCEPT [ssh-userauth] -- OK
I SENT: USERAUTH_REQUEST [none]
I RECV: USERAUTH_FAILURE, continuations [publickey, password, keyboard-interactive]
I SEND: Disconnect packet: The user canceled authentication.
I Changing state from STATE_CONNECTION to STATE_SEND_DISCONNECT
I Changing state from STATE_SEND_DISCONNECT to STATE_CLOSED
I Connected for 1 seconds, 1113 bytes sent, 1764 bytes encoded ed
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.