> Not looking to use openssh. > The powers that be declared SSH to be used. > > And if not xinetd, then how do I setup this service ? > > Thanks! > > -dan > > > Once upon a time, RHL71 wrote : > > > > > Hey all, > > > > > > I'm running RedHat 7.1 and using xinetd as opposed to > inetd for the > > > first time. > > > Everything appears to be working well except one critical > > service, SSH. > > > Has anyone managed to run SSH, not openssh, via Xinetd > > successfully ? If > > > so, > > > could you supply your configuration file so I can try it here ? > > > Just for some background, it's RedHat 7.1, Kernel 2.4.9-6 > and Secure > > > Shell 3.0 > > > > > > Thanks much! > > > > Why do you want to run ssh through xinetd when you have a > > fully-functionnal > > standalone openssh by default? Also, I do not think (x)inetd is the > > recommended way to run (open)ssh... > > > > Matthias > > > > -- > > Clean custom Red Hat Linux RPMs : http://freshrpms.net/ > > Red Hat Linux release 7.2 (Enigma) running kernel 2.4.9-7 > > Load : 0.00, AC on-line, battery charging: 100% (11:22)
There are reasons to use SSH 3 instead of openssh (like going through a SOCKS proxy--which I could never quite do cleanly with dante/openssh). If you are serious about using the commercial ssh, you should first disable/remove openssh: chkconfig --level 2345 sshd off Then make sure the sshd2 file is in /etc/init.d/ (I think that the rpm package should install it there by default). Enable sshd2: chkconfig sshd2 on The commercial ssh rpm installs the ssh2, sftp2, etc. files in /usr/local/bin, as well as symlinks. So, if your path has /usr/local/bin before /usr/bin, you can just use ssh (instead of ssh2). I simply removed the openssh packages, and just use ssh. Forrest _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
