[cobalt-users] Shell access: Disabling Telnet

["Tim Bolt" <timbolt@xxxxxxxxxxx>]

> > 4) What if SSH goes 'wonky'?  As mentioned in:
> > http://list.cobalt.com/pipermail/cobalt-users/2000-October/022643.html
> > this can be a costly issue to reboot then!  Should I not
> > rely on SSH and rely on a "no-use" policy for telnet?

> I cannot honestly say I ever recall a time when sshd crapped out and
> denied me access to a box. This includes one that *is* 6000 miles 
> away,
> If sshd broke, I'd actually have to fly there and fix it myself! 
> (Not
> that I'd mind, but it would be mighty inconvenient and VERY
> expensive)ssh is rugged and not known for going down without 
> reason. I
> rely on it, and I believe you should too. It's "trustworthy"

> BTW...I don't read that archive message the way you do. I don't 
> think it
> says anything about ssh going wonky...but maybe I read it wrongly.

No, you read it right, my reference to it focussed on the cost of having one of the DataCentre guys go in and press the reboot button and such.

SSH (& OpenSSH ?) do seem simple enough they should be robust, but with the keys and such problems can occur.  I know a uni server where the SSH CLIENT installed would not let us SSH from the box to another box.

I do not know of any definite problems, but my impression during installaion and use elsewhere is SSH is still not quite as robust as it should be.

I am willing to rely on it though.

Thanks,
Tim

PS - Whats this about using SSH for FTPing as well?
Any references?  Same daemon receive the login?  Special FTP client needed?

------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/