> How about, as a service to enable as you are updating SSH remotely from
> the other side of the country to fix the most recent problem security
> problem and need a backup system to get into the server in the event
> that something goes wrong?
Maybe it would work as well, to start a ssh daemon on
> If you need this on as the norm, please at least use TCP wrappers to
> limit from where it can be accessed, and change any used passwords
> immediately after reestablishing control.
I think the real insecurity in telnet comes not from buffer-overflows
and whatnot, but rather from people sniffin
> So the solution to not run a backup telnet server for updating SSH is to
> run a second, known insecure version of sshd on a different port,
> presuming of course, that you are allowed to run said sshd on said high
> port in the first place.
Sorry, that was stupid of me. First build the new sshd
> Yo Andrew!
... Right.
> Then you update OpenSSL and it crashes all the ssh processes at the same
> time. Been, there, done that.
Thanks a lot.
After your suggestion that it couldn't be done, I tried it. While it
took thinking, I could have done it had I not killall'ed my sshd's
without changin
