Is it possible that a server that doesn't anticipate/ does not support environment variables from clients, terminate such sessions upon noticing the client sending such variables?
I have captured debug level logs for the sftp client, everything goes fine until the very end i.e successful authentication, request for sftp subsystem. At this stage, when client sends env variables, the server closes the session.
Another sftp client, runs to completion of the session, as that one is not sending any env data.
I am aware of AcceptEnv, SendENv features in openssh s/w, but is this behavior warranted on behalf of the proprietary sftp/ssh server (to drop a session from a client that tries to send env data)?
debug1: channel request 0: subsystem debug2: callback done debug1: channel 0: open confirm rwindow 32000 rmax 35000 debug1: channel_free: channel 0: client-session, nchannels 1 debug3: channel_free: status: The following connections are open: #0 client-session (t4 r43 i0/0 o0/0 fd 6/7) debug3: channel_close_fds: channel 0: r 6 w 7 e 8 debug1: fd 0 clearing O_NONBLOCK debug2: fd 1 is not O_NONBLOCK debug1: fd 2 clearing O_NONBLOCK Connection to xyz.com closed by remote host.