Almost there!

ssh -d

almost works.
It starts sshd, and leaves it running, attached to the shell's terminal.
I can ssh in from localhost, and also from horse (shell.clug.net.nz,
thanks Craig!) through my firewall. However, once the session is
finished (or the password/username is incorrect 3 times in a row),
then ssh -d exits. Maybe it isn't forking correctly for each
connection?

Cheers,
Carl.

On 14/08/05, Nick Rout <[EMAIL PROTECTED]> wrote:
> On Sat, 2005-08-13 at 22:08 +1200, Carl Cerecke wrote:
> > OK. I've updated openssh from yast online update. (No, I had no
> > security updates or anything.
> > Yes, I'm a bad boy. I'll blame it on having had a dial-up only for so long.)
> >
> > The rpm checks out OK. This is what happens when I try to start sshd.
> > First, using the
> > rc script, then directly:
> > linux:~ # rcsshd start
> > Starting SSH daemon
> >                failed
> > linux:~ # sshd
> > linux:~ # ssh 127.0.0.1
> > ssh: connect to host 127.0.0.1 port 22: Connection refused
> > linux:~ # rpm -qf `which sshd`
> > openssh-3.8p1-37.17
> > linux:~ #
> >
> > Just to prove to you doubters that it really does kind-of connect OK
> > to port 22, here's
> > the output from strace:
> >
> > socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
> > connect(3, {sa_family=AF_INET, sin_port=htons(22),
> > sin_addr=inet_addr("0.0.0.0")}, 16) = 0
> > getsockname(3, {sa_family=AF_INET, sin_port=htons(32776),
> > sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
> > close(3)                                = 0
> >
> >
> > That last close is a bit suspicious. Especially because there were no
> > dup/dup2 calls. Yes,
> > I did an ltrace also - but it didn't help either.
> >
> > I even tried "rcSuSEfirewall2 stop" before trying to start sshd, but
> > no joy either.
> >
> > Giving up for the night,
> > Carl.
> 
> I am just wondering if you have tried starting sshd manually with the -d
> option - from the man page:
> 
> "-d      Debug mode.  The server sends verbose debug output to the
> system log, and does not put
>              itself in the background.  The server also will not fork
> and will only process one con-
>              nection.  This option is only intended for debugging for
> the server.  Multiple -d options
>              increase the debugging level.  Maximum is 3."
> 
> 
> 
> 
> 
> --
> Nick Rout <[EMAIL PROTECTED]>
> 
>

Reply via email to