Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Discussion of open issues, suggestions and bugs regarding network security and data protection solution - SecureBridge
Post Reply
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Thu 04 Apr 2019 20:28

Hi,
have you guys seen this error?
SSH CHannel ERROR:Unsupported file attributes data
(They are uploading a file to my Securebridge SFTP server)

The client authenticates and logs in fine with a DSA key and this error happens when they upload a file.

Not sure what client they are using but from a screen shot they sent me it appears to be the linux SSH command line client.
I have a request to get the actual version from them.

it works fine with every client I have so it's either they are using a really old version of the SFTP client or a really new one.

UPDATE, they are using this client: Reflection for Secure IT 8.0.1.74 on x86_64-redhat-linux-gnu (64-bit).
Never heard of it before, but it appears to be a proprietary client from microfocus?
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 15:18

Just updated my sbridge to the 9.0.1 release from feb and will be testing to see if newer version takes care of it.
UPDATE: works fine with filezilla putty and putty based clients and OpenSSH command line. Waiting on user to test their proprietary client.
Top
ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by ViktorV » Fri 05 Apr 2019 15:27

Unfortunately, we can't reproduce the issue.
We downloaded the test version of Reflection for Secure IT Client for UNIX 8.0.2.138 and were able to upload the file to the latest version of TScSFTPServer without errors. Please try using the latest versions of both SecureBridge and Reflection for Secure IT Client for UNIX and let us know the result.
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 15:46

Hi,
They just tried to upload a file with latest version of Sbridge and this is what I am getting:

04/05/2019 10:33:47 AM:[Connect] New SFTP (Before) connection from 1xxxxxx2:33388
04/05/2019 10:33:48 AM:[Error] SSH Client(0.0.0.0:16390) ERROR for user:N/A:Format of server version is invalid ()
04/05/2019 10:34:51 AM:[Connect] New SFTP (Before) connection from xxxxxxxx:33418
04/05/2019 10:34:56 AM:[Logon] User crds_user logged in from xxxxxxxxx:33418 (Auth Type=SFTP Pubkey Keyname=crds_public_key)
04/05/2019 10:34:56 AM:[Connect] New SFTP (after) connection from xxxxxxxx:33418 (crds_user)
04/05/2019 10:35:11 AM:[Error] SSH CHannel ERROR:Unsupported file attributes data
04/05/2019 10:35:11 AM:[Logoff] User crds_user disconnected

So it appears it may be they are using a really old version of their client, any ideas on how to get it to work without them updating to the latest client? its a corporate instance and they don't like to update.
Last edited by tcaduto12068 on Fri 05 Apr 2019 15:47, edited 1 time in total.
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 15:47

Hi,
They just tried to upload a file with latest version of Sbridge and this is what I am getting:

04/05/2019 10:33:47 AM:[Connect] New SFTP (Before) connection from xxxxxx:33388
04/05/2019 10:33:48 AM:[Error] SSH Client(0.0.0.0:16390) ERROR for user:N/A:Format of server version is invalid ()
04/05/2019 10:34:51 AM:[Connect] New SFTP (Before) connection from xxxxxx:33418
04/05/2019 10:34:56 AM:[Logon] User crds_user logged in from xxxxxx.92:33418 (Auth Type=SFTP Pubkey Keyname=crds_public_key)
04/05/2019 10:34:56 AM:[Connect] New SFTP (after) connection from xxxxxxxxxxx:33418 (crds_user)
04/05/2019 10:35:11 AM:[Error] SSH CHannel ERROR:Unsupported file attributes data
04/05/2019 10:35:11 AM:[Logoff] User crds_user disconnected

So it appears it may be they are using a really old version of their client, any ideas on how to get it to work without them updating to the latest client? its a corporate instance and they don't like to update.
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 17:25

I was able to install their windows client and I can upload a file and that version is newer than the one you guys tested with on Linux.

There are other issues now, their junky client now crashes when it does a ls / with this error:

Enter password for [email protected]:
/>ls /
fatal: buffer_get_string: bad string length 2032127
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 19:29

using the latest Reflection SFTP/FTP GUI client any dir listing does this:
(uploads work)

LS
2019-04-05 15:38:59:833 debug3: absolute path: (null) --> (null)
2019-04-05 15:38:59:833 debug3: Sending SSH2_FXP_OPENDIR (7) /
2019-04-05 15:38:59:843 debug3: Sending SSH2_FXP_READDIR "" (8)
2019-04-05 15:38:59:874 debug3: Received reply T:104 (8)
2019-04-05 15:38:59:874 debug3: Received 3 SSH2_FXP_NAME responses
fatal: buffer_get_string: bad string length 2032127
listing complete for current directory - error
A Secure Shell error occurred.
(5) Bad message.

Maybe a unicode issue?
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Fri 05 Apr 2019 21:22

some other info, if I set the reflection client to Unix instead of NT I get this before it crashes:

/
Assuming Unix FTP Server
Determining token count ...
LS -lad .*

Then it crashes and disconnects from Sbridge server.

If I set the server type to NT it won't crash and just gives that bad message error I posted before.

I also turned off the use unicode option in the Sbridge server but that made no difference.
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Tue 09 Apr 2019 13:15

any ideas on how to get the dir listings to work with the Reflection SFTP client?
It's odd that every other client I have tested works fine with the Sbridge SFTP server except this one...it's almost as if they came up with some semi compatible SFTP protocol on their own LOL
Top
ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by ViktorV » Wed 10 Apr 2019 13:17

tcaduto12068 wrote: ↑Fri 05 Apr 2019 15:47 Hi,
They just tried to upload a file with latest version of Sbridge and this is what I am getting:

04/05/2019 10:33:47 AM:[Connect] New SFTP (Before) connection from xxxxxx:33388
04/05/2019 10:33:48 AM:[Error] SSH Client(0.0.0.0:16390) ERROR for user:N/A:Format of server version is invalid ()
04/05/2019 10:34:51 AM:[Connect] New SFTP (Before) connection from xxxxxx:33418
04/05/2019 10:34:56 AM:[Logon] User crds_user logged in from xxxxxx.92:33418 (Auth Type=SFTP Pubkey Keyname=crds_public_key)
04/05/2019 10:34:56 AM:[Connect] New SFTP (after) connection from xxxxxxxxxxx:33418 (crds_user)
04/05/2019 10:35:11 AM:[Error] SSH CHannel ERROR:Unsupported file attributes data
04/05/2019 10:35:11 AM:[Logoff] User crds_user disconnected

So it appears it may be they are using a really old version of their client, any ideas on how to get it to work without them updating to the latest client? its a corporate instance and they don't like to update.
As we have already written, unfortunately, we could not reproduce the problem. Please ask your customers to connect to your server using the -D 3 parameter and send the log to us. For example:

Code: Select all

sftp -D 3 [email protected]
Top
ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by ViktorV » Wed 10 Apr 2019 13:18

tcaduto12068 wrote: ↑Tue 09 Apr 2019 13:15 any ideas on how to get the dir listings to work with the Reflection SFTP client?
It's odd that every other client I have tested works fine with the Sbridge SFTP server except this one...it's almost as if they came up with some semi compatible SFTP protocol on their own LOL
Please specify if you tested the Windows version of the Reflection SFTP / FTP GUI Client with other SFTP servers?
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Wed 10 Apr 2019 15:11

Hi,
I only tested the win32 version of their client with the Sbridge SFTP server.

I can try it with a OpenSSH SFTP server on Ubuntu, that's the only other one I have access to.
I will post results later.
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Wed 10 Apr 2019 15:16

I tested the reflection client against the SFTP server that ships with Ubuntu server 16.04.6 LTS
It works, here is the console output from the Reflection client:

SFTP version 3
PWD
/home/sft_admin
Assuming UNIX FTP server
Determining token count ...
LS -lad .*
listing complete for -lad .* - does not exist
Assuming 9 tokens per line.
LS
listing complete for current directory
drwx------ 2 sft_admin sft_admin 4096 Apr 27 2017 .ssh
drwxr-xr-x 3 root root 4096 Apr 27 2017 .
drwxr-xr-x 5 root root 4096 Apr 27 2017 ..
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Wed 10 Apr 2019 16:33

Debug output from the older reflection client:
This is the initial connection, waiting on them to send the put.

Code: Select all

[crdsmft@crdsbcclprapp03 ~]$ sftp -D 3 -P 10022 [email protected]
2019-04-10 12:18:17  debug(3) pid=4662 mapPath @SYSCONFDIR@/ssh2_config -> /etc/ssh2/ssh2_config
2019-04-10 12:18:17  debug(3) pid=4662 mapPath @BINDIR@/ssh -> /usr/bin/ssh
2019-04-10 12:18:17  debug(3) pid=4663 dlopen /usr/lib64/libgssapi_krb5.so
2019-04-10 12:18:17  debug(3) pid=4663 gss_initialize: dlopen failed: /usr/lib64/libgssapi_krb5.so: cannot open shared object file: No such file or directory
2019-04-10 12:18:17   verbose pid=4663 GSSAPI mechanisms will be disabled because the following shared libraries could not be loaded: /usr/lib64/libgssapi_krb5.so
2019-04-10 12:18:17  debug(1) pid=4663 Connecting to xxx.xxxxx.xxxx [xxx.xxx.xxx.xxx] port 10022 address family IPv4.
2019-04-10 12:18:17  debug(2) pid=4663 HPN: is disable. Not setting SO_RCVBUF.
2019-04-10 12:18:17  debug(1) pid=4663 Connection established to xxx.xxx.xxx.xxx.
2019-04-10 12:18:17  debug(3) pid=4663 Identification file: /export/se/crdsmft/.ssh2/identification
2019-04-10 12:18:17  debug(3) pid=4663 Identity file /export/se/crdsmft/.ssh2/crdsndm@crds read from identification file /export/se/crdsmft/.ssh2/identification
2019-04-10 12:18:17  debug(3) pid=4663 key_from_blob(0x159a4a0, 818)
2019-04-10 12:18:17  debug(3) pid=4663 single_cert_from_blob: We have 818 bytes available in BIO
2019-04-10 12:18:17  debug(3) pid=4663 single_cert_from_blob: read X509 from BIO failed
2019-04-10 12:18:17  debug(3) pid=4663 key_from_blob(..., ...) ktype=ssh-dss
2019-04-10 12:18:17  debug(2) pid=4663 Load RFC 4716 compliant public key type 1 successfully from file /export/se/crdsmft/.ssh2/[email protected]
2019-04-10 12:18:17  debug(1) pid=4663 key file /export/se/crdsmft/.ssh2/crdsndm@crds type 1
2019-04-10 12:18:17  debug(1) pid=4663 Remote protocol version 2.0, remote software version Devart-8.0
2019-04-10 12:18:17  debug(1) pid=4663 remote ssh is not hpn-aware: Devart-8.0
2019-04-10 12:18:17  debug(1) pid=4663 Local version string SSH-2.0-ReflectionForSecureIT_8.0.1.74
2019-04-10 12:18:17  debug(2) category(Network)  pid=4663 fd 3 setting O_NONBLOCK
2019-04-10 12:18:17  debug(1) pid=4663 Disabling compression in myproposal
2019-04-10 12:18:17  debug(1) pid=4663 SSH2_MSG_KEXINIT sent
2019-04-10 12:18:17  debug(1) pid=4663 SSH2_MSG_KEXINIT received
2019-04-10 12:18:17  debug(1) pid=4663 KEX_INIT_SENT
2019-04-10 12:18:17  debug(2) pid=4663 chooseConf: client proposal sent:
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[0] =  diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[1] =  ssh-rsa,ssh-dss,x509v3-rsa2048-sha256,x509v3-sign-rsa,x509v3-sign-dss,[email protected]
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[2] =  aes128-ctr,aes128-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc,blowfish-cbc,3des-cbc,cast128-cbc,arcfour,arcfour128,arcfour256
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[3] =  aes128-ctr,aes128-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc,blowfish-cbc,3des-cbc,cast128-cbc,arcfour,arcfour128,arcfour256
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[4] =  hmac-sha256,hmac-sha2-256,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-sha512,hmac-sha2-512
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[5] =  hmac-sha256,hmac-sha2-256,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-sha512,hmac-sha2-512
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[6] =  none
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[7] =  none
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[8] =
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[9] =
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: first_kex_follows 0
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: reserved 0
2019-04-10 12:18:17  debug(2) pid=4663 chooseConf: server proposal received:
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[0] =  diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,curve25519-sha256
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[1] =  ssh-dss,rsa-sha2-256,rsa-sha2-512,ssh-rsa
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[2] =  3des-cbc,blowfish-cbc,aes128-cbc,aes192-cbc,aes256-cbc,cast128-cbc,3des-ctr,blowfish-ctr,aes128-ctr,aes192-ctr,aes256-ctr,cast128-ctr
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[3] =  3des-cbc,blowfish-cbc,aes128-cbc,aes192-cbc,aes256-cbc,cast128-cbc,3des-ctr,blowfish-ctr,aes128-ctr,aes192-ctr,aes256-ctr,cast128-ctr
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[4] =  hmac-sha1,hmac-sha2-256,hmac-sha2-512,hmac-sha2-224,hmac-sha2-384
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[5] =  hmac-sha1,hmac-sha2-256,hmac-sha2-512,hmac-sha2-224,hmac-sha2-384
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[6] =  none
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[7] =  none
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[8] =
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: proposal[9] =
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: first_kex_follows 0
2019-04-10 12:18:17  debug(2) pid=4663 buf2prop: reserved 0
2019-04-10 12:18:17  debug(2) pid=4663 Mac::init: found hmac-sha2-256
2019-04-10 12:18:17  debug(1) pid=4663 The server will use the following algorithms to communicate with the client: aes128-ctr hmac-sha2-256 none
2019-04-10 12:18:17  debug(2) pid=4663 Mac::init: found hmac-sha2-256
2019-04-10 12:18:17  debug(1) pid=4663 The client will use the following algorithms to communicate with the server: aes128-ctr hmac-sha2-256 none
2019-04-10 12:18:17  debug(1) pid=4663 sending SSH2_MSG_KEX_DH_GEX_REQUEST (1024<4096<8192)
2019-04-10 12:18:17  debug(1) pid=4663 expecting SSH2_MSG_KEX_DH_GEX_GROUP
2019-04-10 12:18:17  debug(2) pid=4663 generateKey: priv key bits set: 253/512
2019-04-10 12:18:17  debug(2) pid=4663 bits set: 2004/4096
2019-04-10 12:18:17  debug(1) pid=4663 sending SSH2_MSG_KEX_DH_GEX_INIT
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(0x159ba20, 278)
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: We have 278 bytes available in BIO
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: read X509 from BIO failed
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(..., ...) ktype=ssh-rsa
2019-04-10 12:18:18  debug(3) pid=4663 mapPath @SYSCONFDIR@/hostkeys -> /etc/ssh2/hostkeys
2019-04-10 12:18:18  debug(3) pid=4663 check_hostkey_in_hostkeys_by_key: hostkeys_dir /export/se/crdsmft/.ssh2/hostkeys
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(0x159e9a0, 278)
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: We have 278 bytes available in BIO
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: read X509 from BIO failed
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(..., ...) ktype=ssh-rsa
2019-04-10 12:18:18  debug(2) pid=4663 Load RFC 4716 compliant public key type 0 successfully from file /export/se/crdsmft/.ssh2/hostkeys/key_10022_adt-pakwdrftp01.mi.micorp.com,xxx.xxx.xxx.xxx.pub
2019-04-10 12:18:18  debug(1) pid=4663 check_hostkey_in_hostkeys_by_key: key matches file /export/se/crdsmft/.ssh2/hostkeys/key_10022_xxxxxxxxxx,xxx.xxx.xxx.xxx.pub, returning HOST_OK
2019-04-10 12:18:18  debug(1) pid=4663 Host 'xxxxxxxxx,xxx.xxx.xxx.xxx' is known and matches the RSA host key.
2019-04-10 12:18:18  debug(2) pid=4663 bits set: 2141/4096
2019-04-10 12:18:18  debug(2) pid=4663 ssh_rsa_verify: public key algorithm is ssh-rsa
2019-04-10 12:18:18  debug(1) pid=4663 verifySignature: signature correct
2019-04-10 12:18:18  debug(2) pid=4663 deriveKeys
2019-04-10 12:18:18  debug(2) pid=4663 set_newkeys: mode 1
2019-04-10 12:18:18  debug(1) pid=4663 SSH2_MSG_NEWKEYS sent
2019-04-10 12:18:18  debug(1) pid=4663 expecting SSH2_MSG_NEWKEYS
2019-04-10 12:18:18  debug(2) pid=4663 set_newkeys: mode 0
2019-04-10 12:18:18  debug(1) pid=4663 SSH2_MSG_NEWKEYS received
2019-04-10 12:18:18  debug(1) pid=4663 SSH2_MSG_SERVICE_REQUEST sent
2019-04-10 12:18:18  debug(2) pid=4663 service_accept: ssh-userauth
2019-04-10 12:18:18  debug(1) pid=4663 SSH2_MSG_SERVICE_ACCEPT received
2019-04-10 12:18:18  debug(2) pid=4663 added key: /export/se/crdsmft/.ssh2/crdsndm@crds (0x159be40)
2019-04-10 12:18:18  debug(3) pid=4663 input_userauth_banner
Welcome to the XXX Managed SFTP Server2019-04-10 12:18:18  debug(3) pid=4663 Client authentication methods:
2019-04-10 12:18:18  debug(3) pid=4663
        publickey
        keyboard-interactive
        password
2019-04-10 12:18:18  debug(3) pid=4663 Server authentication methods:
2019-04-10 12:18:18  debug(3) pid=4663
        password
        publickey
2019-04-10 12:18:18  debug(2) pid=4663 Querying server for authmethod - publickey
2019-04-10 12:18:18  debug(1) pid=4663 Offering algorithm ssh-dss, public key: /export/se/crdsmft/.ssh2/crdsndm@crds
2019-04-10 12:18:18  debug(1) pid=4663 Server accepts key: pkalg ssh-dss blen 818
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(0x159de70, 818)
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: We have 818 bytes available in BIO
2019-04-10 12:18:18  debug(3) pid=4663 single_cert_from_blob: read X509 from BIO failed
2019-04-10 12:18:18  debug(3) pid=4663 key_from_blob(..., ...) ktype=ssh-dss
2019-04-10 12:18:18  debug(2) pid=4663 input_userauth_pk_ok: fp df:cb:f3:07:68:4b:c8:0b:96:94:3d:14:d4:2a:64:f0
2019-04-10 12:18:18  debug(3) pid=4663 sign_and_send_pubkey
2019-04-10 12:18:19      info pid=4663 Authentication successful.
2019-04-10 12:18:19  debug(2) category(Network)  pid=4663 fd 4 setting O_NONBLOCK
2019-04-10 12:18:19  debug(3) category(Network)  pid=4663 fd 5 is O_NONBLOCK
2019-04-10 12:18:19  debug(1) pid=4663 HPN: Remote server is not HPN-aware.
2019-04-10 12:18:19  debug(1) pid=4663 HPN: Final HPNBufferSize: 2097152 bytes
2019-04-10 12:18:19  debug(2) pid=4663 HPN: disabled=0
2019-04-10 12:18:19  debug(2) pid=4663 HPN: Final TCP window size: 2097152 bytes
2019-04-10 12:18:19  debug(1) pid=4663 channel 0: new [client-session]
2019-04-10 12:18:19  debug(1) pid=4663 HPN: Dynamic window scaling enabled.
2019-04-10 12:18:19  debug(3) pid=4663 ssh_session_open: channel_new: 0
2019-04-10 12:18:19  debug(2) pid=4663 channel 0: send open
2019-04-10 12:18:19  debug(1) pid=4663 Entering interactive session.
2019-04-10 12:18:19  debug(2) pid=4663 callback start
2019-04-10 12:18:19  debug(2) pid=4663 sendSubsystem: id 0
2019-04-10 12:18:19  debug(1) pid=4663 Sending subsystem: sftp
2019-04-10 12:18:19  debug(2) pid=4663 channel 0: request subsystem confirm true
2019-04-10 12:18:19  debug(2) category(Network)  pid=4663 fd 3 setting TCP_NODELAY
2019-04-10 12:18:19  debug(2) pid=4663 callback done
2019-04-10 12:18:19  debug(2) pid=4663 channel 0: open confirm rwindow 1048576 rmax 131072
2019-04-10 12:18:19  debug(2) pid=4663 Request for subsystem "sftp" succeeded on channel 0
2019-04-10 12:18:19  debug(2) category(Xfer.Protocol)  pid=4662 Remote SFTP version: 4
2019-04-10 12:18:19  debug(2) category(Xfer.Protocol)  pid=4662 Init extension: "newline"
2019-04-10 12:18:19  debug(2) category(Xfer.Protocol)  pid=4662 Newline convention from extension is: <CR><LF>
2019-04-10 12:18:19  debug(3) category(Xfer.Protocol)  pid=4662 sending SSH_FXP_REALPATH request for .
2019-04-10 12:18:19  debug(3) category(Xfer.Protocol)  pid=4662 Sent message fd 3 T:16 I:1
2019-04-10 12:18:19  debug(3) category(Xfer.Protocol)  pid=4662 SSH_FXP_REALPATH . -> /
sftp>
Top
tcaduto12068
Posts: 132
Joined: Wed 17 Aug 2016 05:57

Re: Getting this error( SSH CHannel ERROR:Unsupported file attributes data) when client tries to upload file

Post by tcaduto12068 » Wed 10 Apr 2019 16:39

Debug output from the put:

Code: Select all

sftp> put test_10042019.txt
2019-04-10 12:35:20  debug(3) category(Xfer.Misc)  pid=29619 parse_args: cmd=put, cp=test_10042019.txt
2019-04-10 12:35:20  debug(3) category(Xfer.Misc)  pid=29619 copying: test_10042019.txt to /
2019-04-10 12:35:20  debug(1) category(Xfer.Misc)  pid=29619 do_stat complete
2019-04-10 12:35:20  debug(3) category(Xfer.Protocol)  pid=29619 sending SSH_FXP_STAT request for /
2019-04-10 12:35:20  debug(3) category(Xfer.Protocol)  pid=29619 Sent message fd 3 T:17 I:2
2019-04-10 12:35:22  debug(3) category(Xfer.Protocol)  pid=29619 Received stat reply T:105 I:2
2019-04-10 12:35:22  debug(2) category(Xfer.Misc)  pid=29619 SmartFileTransfer is not available on server - skipping hash calculation.
2019-04-10 12:35:22  debug(3) category(Xfer.Protocol)  pid=29619 sending SSH_FXP_STAT request for /test_10042019.txt
2019-04-10 12:35:22  debug(3) category(Xfer.Protocol)  pid=29619 Sent message fd 3 T:17 I:3
2019-04-10 12:35:22  debug(3) category(Xfer.Protocol)  pid=29619 Received stat reply T:101 I:3
2019-04-10 12:35:22  debug(1) category(Xfer.Misc)  pid=29619 Couldn't stat remote file: no such file
2019-04-10 12:35:22  debug(3) category(Xfer.Misc)  pid=29619 Destination file /test_10042019.txt exists: No
2019-04-10 12:35:22  debug(3) category(Xfer.Protocol)  pid=29619 Sent message SSH_FXP_OPEN I:4 P:/test_10042019.txt
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: rcvd close
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: output open -> drain
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: close_read
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: input open -> closed
2019-04-10 12:35:22  debug(3) pid=29620 channel 0: will not send data after close
2019-04-10 12:35:22  debug(2) pid=29620 : channel 0: obuf empty
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: close_write
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: output drain -> closed
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: almost dead
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: gc: notify user
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: gc: user detached
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: send close
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: is dead
2019-04-10 12:35:22  debug(2) pid=29620 channel 0: garbage collecting
2019-04-10 12:35:22  debug(1) pid=29620 channel 0: free: client-session, nchannels 1
2019-04-10 12:35:22  debug(3) pid=29620 channel 0: close_fds r -1 w -1 e 6 c -1
2019-04-10 12:35:22  debug(3) pid=29620 channel 0: status:
2019-04-10 12:35:22  debug(1) category(Network)  pid=29620 fd 0 clearing O_NONBLOCK
2019-04-10 12:35:22  debug(3) category(Network)  pid=29620 fd 1 is not O_NONBLOCK
2019-04-10 12:35:22  debug(1) pid=29620 Transferred: stderr 0 bytes in 14.2 seconds
2019-04-10 12:35:22  debug(1) pid=29620 Bytes per second: stderr 0.0
2019-04-10 12:35:22  debug(1) pid=29620 ClientLoop::execute() returns -1
child process (ssh) exited with code 255.
Top
Post Reply

Return to “SecureBridge”