Date: Wed, 11 Oct 2000 20:45:32 -0700 From: Kent Stewart <kstewart@urx.com> To: Alan Clegg <abc@bsdi.com> Cc: Kevin LEE <klee@esec.com.au>, "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG> Subject: Re: HowTo generate ssh_host_dsa_key key pairs Message-ID: <39E533DC.C133F52@urx.com> References: <39E50C1A.FF9FFB55@esec.com.au> <39E513E4.7EE47315@urx.com> <20001011221536.B35107@diskfarm.firehouse.net> <39E527A4.C614E5A9@urx.com> <20001011230136.E35799@diskfarm.firehouse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alan Clegg wrote: > > Unless the network is lying to me again, Kent Stewart said: > > > I hadn't seen that but ssh wouldn't connect to the remote site until I > > did it manually. > > Had you rebooted after mergemastering? I didn't like sitting there with a modified world and an old 4.0 kernel. I usually reboot immediately after running mergemaster. The real question is probably when I set sshd_enable="YES". I think I did that after the cvsup from 4.0-R to 4.1.1-Stable and build sequence. I don't think I tried using ssh to logon until the modified kernel was built and installed, which produced one more boot after that. Too many loose ends to worry about right now. If I had thought it was supposed to work, I would have done a better job of paying attention to what I did. I had one system that multi-boots W2K and FreeBSD, which hadn't been upgraded to sshd_enable="YES". I modified rc.conf and rebooted it. I could see it generate the key during the boot. I was also able to use ssh to login. I'm assuming I did something wrong on the first system that made it not work. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39E533DC.C133F52>