Atro, thanks for your input. I don't have any rights on the BSDI box; it
belongs to an ISP. I don't think the problem is on the BSDI side because I've
connected to that box from Windows successfully for more than 2 years.
After more than a week of fighting with OpenSSH (on Irix; my Linux compilation
went flawlessly), I broke down and used the package from F-Secure -- it compiled
with no issues. I had to install SSH1 then SSH2 to get compatibility for both
protocols and noticed that the ssh1 client that was part of the SSH1
installation connected to the BSDI box with no problems, but the ssh1 client
that replaced it from the SSH2 installation hung. So, I'm just using the ssh1
client from the SSH1 installation and all seems to be working.
miguel.
Atro Tossavainen wrote:
> Hello Miguel,
>
> > The problem is that the Irix -> BSDI connection is hanging, timing out,
> > trying to use rsh, then dieing altogether. The BSDI -> Irix connection
> > works fine. Any ideas on what could be the problem?
>
> The BSDI is probably not running the ssh daemon (the server part of the
> program).
>
> Try telnetting to the BSDI box port 22 ("telnet hostname 22") and see if
> you get anything. If it looks like it's connecting but nothing useful
> ever comes out (the SSH-1.5-1.2.26 banner), you've got a faulty daemon
> running on the BSDI and need to look into why it doesn't work, but if
> you instantly get a "Connection refused" message, you don't have the
> daemon running at all and starting it should be enough to solve the
> problem.
>
> I've seen it at least once that a faulty sshd would open up the listener
> on port 22, and would accept connections, but could not do anything use-
> ful with them. This was on IRIX, when I tried compiling the daemon with
> the -O3 optimization flag. Using -O3 broke the key generation and the
> daemon hung in an endless loop, generating keys, testing them, failing,
> generating new keys, testing them, failing, and so on.
>
> I proposed changes (not actual code, but ideas) to the effect that sshd
> should not open up a listener before it has generated keys, and also,
> that it should detect the endless loop of failing to generate keys and
> die instead of continuing to occupy all of the computer's CPU time...
> but as far as I know, ssh1 still does this the same old way.
>
> If you suspect you have a broken daemon, run it on the BSDI with -d
> ("sshd -d") to see why it won't start up properly.
>
> --
> Atro Tossavainen (Mr.) / The Institute of Biotechnology at
> Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
> +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
> < URL : http : / / www . iki . fi / atro . tossavainen / >
