From: Patata Kid on
Hi all again.
I have just discovered why the ssh daemon didn't start the sftp subsystem.

The problem was in the configuration file of bash (.bashrc) witch was (is)
the default shell for the accounts used to connect.
Another person for some unknown (to me!) reasons added the line "sttys
-istrip" at the end of that file.

For this reason the client was unable to open the connection,... I suppose
the client was at fault because I read "connection closed by client" in the
sshd log.
Removed the line and all is OK now,... I have just to discover why is wad
added! :-)

Hope this could be helpful to someone...

Kind regard to all and, anyway, thanks for the answers!


"Patata Kid" <none(a)none.com> ha scritto nel messaggio
news:pan.2009.09.01.18.54.04.411794(a)none.com...
> Hi all.
> I have a *strange* problem with my Solaris 10 installation.
>
> Simply put, the ssh daemon does *not* allow *any* user to connect via
> SFTP, even if I have placed the line:
> "Subsystem sftp /usr/lib/ssh/sftp-server" in my
> /etc/sshd/sshd_config file.
>
> The client reports a "error 128" when someone tries to connect, but the
> connection doesn't start.
> Strange is that if I comment the above line the connection *is* accepted!
> (gulp!)
>
> By the way,... the "normal" ssh connection *does* work,... I really do not
> understand why it refuses the sftp connection.
>
> Can someone help me to resolve this mystery?
>
> P.S. I do not have any firewall active (the connection generates from my
> internal network),...
>
> I Googled and googled without any results...
>
> Thanks a lot.
>
> Patata.



From: Velociraptor on
On Sep 8, 10:32 am, "Patata Kid" <n...(a)none.com> wrote:
> Hi all again.
> I have just discovered why the ssh daemon didn't start the sftp subsystem..
>
> The problem was in the configuration file of bash (.bashrc) witch was (is)
> the default shell for the accounts used to connect.
> Another person for some unknown (to me!) reasons added the line "sttys
> -istrip" at the end of that file.

Thanks for posting your info about the problem. I had a similar issue
from having:

stty stop undef
stty start undef

in my .bashrc file. Removing those fixed the issue.

Seems sftp is more sensitive to the shell environment than ssh.

=V=