On Sat, 2005-08-13 at 22:19 +1200, Steve Holdoway wrote:
> >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
> >
> >
> Tried it myself. Next line is...
>
> open("/etc/ssh/ssh_host_rsa_key", O_RDONLY|O_LARGEFILE) = 3
>
> Any problems with that file? files owned root:root, perms 600 on my
> system.
Is it possible that the host key hasn't been created? (This may be a red
herring as according to Carl the strace doesn't even reveal the key file
being searched for).
In my humble experience distros either create a host key when the ssh
daemon is installed, or have a test in the initscript so that one is
created on the first startup of the daemon (or a subsequent startup if
the key has for some reason been deleted.)
I'm not sure how suse deals with creating the host key, and it doesn't
seem likely that they would drop the ball on this, but it might be worth
checking that one has been created.
--
Nick Rout <[EMAIL PROTECTED]>
