From owner-freebsd-current Fri Mar 10 17:43:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 59EC737BBBC; Fri, 10 Mar 2000 17:43:41 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id TAA06836; Fri, 10 Mar 2000 19:43:40 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma006703; Fri Mar 10 19:43:09 2000 Message-Id: <4.3.2.20000310193411.00ac1f00@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 10 Mar 2000 19:40:56 -0600 To: Kris Kennaway From: "Jeffrey J. Mountin" Subject: Re: no openssh after build Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.20000308100755.008639c0@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:35 PM 3/8/00 +0000, Kris Kennaway wrote: >On Wed, 8 Mar 2000, Jeffrey J. Mountin wrote: > > > What I did not check is removing RSAref after a buildworld and checking for > > breakage, but that smacks of shooting one's self in the foot. > >That should just revert to the previous case of complaining loudly if you >try and make use of RSA. Well, so it does. Think I'll go soak my foot. ;) Tried it with RC3 and what is better than the last time is that after installing RSAref one does *not* have to restart sshd in order for RSA authentication to work. Very nice. Still has the problem with other not having permissions on the .ssh dir and authorized_keys file. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message