From owner-freebsd-security Tue Feb 13 10:21:20 2001 Delivered-To: freebsd-security@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 58C5E37B491 for ; Tue, 13 Feb 2001 10:21:13 -0800 (PST) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id PAA80175; Tue, 13 Feb 2001 15:22:59 -0300 (ART) From: Fernando Schapachnik Message-Id: <200102131822.PAA80175@ns1.via-net-works.net.ar> Subject: Re: How to rebuild ssh w/ latest sources (was Re: SSH Vulnerability) In-Reply-To: <200102091841.f19IfNQ84385@earth.backplane.com> "from Matt Dillon at Feb 9, 2001 10:41:23 am" To: Matt Dillon Date: Tue, 13 Feb 2001 15:22:59 -0300 (ART) Cc: Mason Harding , security@FreeBSD.ORG Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org En un mensaje anterior, Matt Dillon escribió: > Yes. If your sources are reasonably up to date (since Jan 23), > just rebuild it: > > cd /usr/src/secure/lib/libssh > make clean obj all This is driving me crazy. A 4.1.1-RELEASE. Cvsuped src-secure and src-crypto. Updated /usr/share/mk, /etc/defaults/make.conf, and still: cc -O -pipe -DSKEY -DNO_IDEA -c /usr/src/secure/lib/libssh/../../../crypto/openssh/authfd.c -o authfd.o In file included from /usr/src/secure/lib/libssh/../../../crypto/openssh/ssh.h:21, from /usr/src/secure/lib/libssh/../../../crypto/openssh/authfd.c:41: /usr/src/secure/lib/libssh/../../../crypto/openssh/rsa.h:20: openssl/bn.h: No such file or directory /usr/src/secure/lib/libssh/../../../crypto/openssh/rsa.h:21: openssl/rsa.h: No such file or directory Any ideas? TIA! Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fschapachnik@vianetworks.com.ar Conmutador: (54-11) 4323-3333 - Soporte: 0810-333-AYUDA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message