From owner-freebsd-current Tue Mar 7 4:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 6126D37BFE3 for ; Tue, 7 Mar 2000 04:50:25 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id NAA16148 for ; Tue, 7 Mar 2000 13:45:20 +0100 (CET) Message-Id: <200003071245.NAA16148@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@freebsd.org Subject: Re: ssh strangeness in -current... Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 07 Mar 2000 13:23:11 +0100." <200003071223.NAA63857@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 07 Mar 2000 13:45:20 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: >Kris Kennaway wrote in list.freebsd-current: > > Without still having seen the error message you were confused by, I c= an't > > do much else to help. I can't think of a better way to explain how to= fix > > the problem than what's currently there. > >As I said in my first message, it complained about a missing >RSA library. (To reproduce the actual error message word by >word, I'd have to install the whole stuff again.) > you have to cvsup the secure stuff from internat. I did that and /usr/bin/ssh works just fine after copying the ssh_* stuff from /usr/local/etc to /etc/ssh. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message