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.

On 1 Sep., 20:54, Patata Kid <n...@none.com> wrote:
> Hi all.
> I have a *strange* problem with my Solaris 10 installation.
>
*snip*

> 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!)

That is indeed weird - Is it possble that you forgot to restart sshd
once or so?

On Sep 1, 7:54=A0pm, Patata Kid <n...@none.com> wrote:
> 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 =A0 =A0 =A0 sftp =A0 /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 no=
t
> 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.

what is does svcs | grep ssh tell you ?

On 2 Sep., 01:08, "Zfs.." <cian.scrip...@gmail.com> wrote:
> On Sep 1, 7:54=A0pm, Patata Kid <n...@none.com> wrote:
>
>
>
> > 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 =A0 =A0 =A0 sftp =A0 /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* accepte=
d!
> > (gulp!)
>
> > By the way,... the "normal" ssh connection *does* work,... I really do =
not
> > understand why it refuses the sftp connection.

Oh, I have an idea ...

With what tool do you connect?

Is it possible that you only allow connecting via ssh 2 and that sftp
client connects try to authenticate via ssh1?

On Tue, 01 Sep 2009 15:10:09 -0700, claus.kick@googlemail.com wrote:

> That is indeed weird - Is it possble that you forgot to restart sshd
> once or so?

Hi,... thanks to you too.

No, I did not forget to restart the service, in fact it is running.
I really do not know where could be the reason of the problem...

By the way,... some time ago the sftp connection DID work,...

On Tue, 01 Sep 2009 16:08:17 -0700, Zfs.. wrote:

> what is does svcs | grep ssh tell you ?

well,... the service is "up and running..."

online         19:21:16 svc:/network/ssh:default

On Wed, 02 Sep 2009 01:33:12 -0700, claus.kick@googlemail.com wrote:

mmm,... I did not think to this aspect,... I use WinSCP to connect to
Solaris.
Thanks for the suggestion,... I will investigate.




> Oh, I have an idea ...
> 
> With what tool do you connect?
> 
> Is it possible that you only allow connecting via ssh 2 and that sftp
> client connects try to authenticate via ssh1?

Patata Kid wrote:

>  By the way,... some time ago the sftp connection DID work,...

Are you sure that the file /usr/lib/ssh/sftp-server exists?

Also, you could put that line in the config file, then truss the ssh
daemon, connect with the sftp client and see what happens.

-- 
 .-.   .-.    Yes, I am an agent of Satan, but my duties are largely
(_  \ /  _)   ceremonial.
     |
     |        dave@fly.srk.fer.hr

On Sep 1, 1:54=A0pm, Patata Kid <n...@none.com> wrote:
> Can someone help me to resolve this mystery?

Run a copy sshd on its own port in debugging mode, like:

sshd -d -p 1234

This will sit there instead of going into the background.  Then, try
your SCP to the port (in the above example, port 1234 instead of 22).
You'll see debugging messages scroll on the screen which will help you
debug the problem.

I think your sshd is only allowing Protocol 2 (which it should!) and
that your winscp only does protocol 1.

On 3 Sep., 14:29, Jim Leonard <mobyga...@gmail.com> wrote:

> I think your sshd is only allowing Protocol 2 (which it should!) and
> that your winscp only does protocol 1.

WinSCP does allowe for Protocol 2, I think the default setting is 1
only.

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@none.com> ha scritto nel messaggio
news:pan.2009.09.01.18.54.04.411794@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.

On Sep 8, 10:32=A0am, "Patata Kid" <n...@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.

=3DV=3D