hi all,
> Try running sshd and sshd2 together but listening on different ports.
>
> For example, you may have a /etc/services file that looks like this:
>
> ssh 22/tcp #Secure Shell 2 Login
> ssh 22/udp #Secure Shell 2 Login
> .....
> .....
> ssh 2022/tcp #Secure Shell 1 Login
> ssh 2022/udp #Secure Shell 1 Login
>
> Otherwise, you'll run into the "Port already in use" stuff.
you'll need unique names for the services in /etc/services otherwise
calls to query service names, e.g. getservbyname will get
confused.
i run multiple ssh1 daemons on single hosts & just specify the
port & ip address for sshd to bind to in the config file.
e.g.
Port 23
ListenAddress 192.168.1.1
& when you fire up sshd - just specify the alternate location
of the daemon config file.
e.g.
/opt/local/sbin/sshd -b 1024 -f /etc/ssh-alternate/sshd_config
this means you need to support multiple locations for key files
etc but that's easy enough to configure for each daemon.
i use the 'chroot' command under solaris to wrap around the second
sshd daemon & one of the side effects of chrooting sshd is that
the path references remain the same for the two ssh daemons,
but are actually different across the file system as one
set of keys/config files etc. is located within the chroot jail.
hope this helps,
pauline
