From owner-freebsd-stable Fri Nov 19 14:34:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 00AEB14DF6 for ; Fri, 19 Nov 1999 14:34:22 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id XAA02792 for freebsd-stable@freebsd.org; Fri, 19 Nov 1999 23:34:21 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA47934 for freebsd-stable@freebsd.org; Fri, 19 Nov 1999 22:52:56 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: OpenSSH for -STABLE? Date: 19 Nov 1999 22:52:55 +0100 Message-ID: <814grn$1epg$1@bigeye.rhein-neckar.de> References: To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > I know that OpenSSH is relatively new, and that a port for it was > recently incorporated into -CURRENT. However, I can't find any > information that would tell me whether or not it's been back-ported > to -STABLE (the port for -CURRENT appears to depend on crypto.1, a > library that does not appear to be found on -STABLE). The OpenSSH port should build on -STABLE, too. It depends on the crypto.1 shared library, which is part of the OpenSSL port. Until very recently, OpenSSL did not build a shared library, so you may need to update that port on your system first. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message