You didn't mention, but I am going to assume that you are using Secure Shell
SSH,
not openSSH.
>Next, since the remote server is located at a local isp, I cannot kill
>ssh2 without killing my connection to the server. When I do this I
>have to call the ISP and ask them to restart it. Unfortunately, they
>are going to get tired of this very soon. I need to kill -HUP sshd2
>to enable permitrootlogin = no. Can I do this from home or am I going
>to have the same kill problem? I guess the question is: Are ssh2 and
>sshd2 separate functions and by killing and restarting sshd2 am I
>going to be kicked from the remote?
Stopping the ssh daemon should not kill current connections. The appropriate
process id should be in /etc/ssh2/sshd2_[PORT#].pid
If you do experience problems with losing connection, maybe set an 'at' job
to
start sshd in X number of minutes, then stop it.
>Next, some of my admins are using secureCRT to get onto the server.
>When I try to use that program, I get a "disconnected, reason 2" What
>is this and what do I have to do to get secureCRT going.
In the /etc/ssh2/sshd2_config file change
CIPHERS AnyCipher
to
CIPHERS AnyStdCipher
That fixed my problem with secureCRT.
>Next, how can I enable ssh1 support so those that want to can login
>under ssh1?
Again in the /etc/ssh2/sshd2_config file you can set the location for
the sshd1 daemon and whether sshd2 should even accept incoming ssh1
requests. You will need ssh 1.2.25 or greater (I think). ssh 1.2.30 is
available.
Just want to remind you that these would most likely be the answers if you
are using
the commercial version of SSH, if your using openSSH it could be a whole
nother story.
Eric
