Date: Wed, 1 Feb 2006 22:31:17 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-questions@freebsd.org Subject: Re: Attention: Garrett Cooper (Was: SSH with Public Key Authentication) Message-ID: <7CDFE393-71FE-40F9-BFEA-0FF3F60636B8@u.washington.edu> In-Reply-To: <1138857366.31138.253348990@webmail.messagingengine.com> References: <1138851222.22515.253344145@webmail.messagingengine.com> <1138851479.22819.253344183@webmail.messagingengine.com> <20060202042447.GA15215@reddwarf.local> <1138857366.31138.253348990@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 1, 2006, at 9:16 PM, david bryce wrote: > > On Wed, 1 Feb 2006 23:24:47 -0500, "Clayton Scott Kern" >> >> What's the permissions for the .ssh directory. I had problems in the >> past if it's not 700. There was an entry in /var/log/messages or its >> equivalent, stating as such. >> >> This would come up on new systems, because I usually had to create >> the >> .ssh directory and the umask would cause it to have 755. >> >> -- >> Clayton Scott Kern >> ckern1@twcny.rr.com The software stated it required >> UNIX System Administrator Microsoft Windows 2000 or higher, >> FreeBSD, Linux, Solaris & so I installed FreeBSD. >> HP-UX > > > Thanks, Clayton! > > It looks like someone has installed the ssh2 package on this machine > (using "pkg_add -r ssh2"). So this is not a standard freebsd ssh > installation. In fact, testing on another box with freebsd 6, I > can connect with Putty using public key authentication. Does > anyone know how to get the standard ssh to work on this machine > without upsetting things too much? It is currently running a > mail server and cvs, so I'm ginger about doing anything radical > on it. Doing a ps -ax shows that it's sshd2 that is running, and > not sshd. But the binaries ARE there for sshd. Except the > hostkey doesn't seem to be there. Could fixing this be as simple > as creating a hostkey for sshd as well, and running it on a > different port than sshd2 is running on? > > Thank you! > > Regards, > > DB > > -- > david bryce > davidbryce@fastmail.fm Add sshd_enable="YES" to /etc/rc.conf and for the time being if you don't want to reboot, run "/etc/rc.d/sshd start". Make sure to turn off and disable sshd2 though (there might be a reference to it in rc.conf as well) by running /usr/local/etc/rc.d/sshd2 stop (or something like that). If you're logged in remotely and don't have physical access to the machine, just run /usr/local/etc/rc.d/sshd2 stop & /etc/rc.d/sshd start. Note the single ampersand--very important. That should stop the first sshd daemon and start the one you want. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7CDFE393-71FE-40F9-BFEA-0FF3F60636B8>