From owner-freebsd-security Thu Mar 7 13:19:59 2002 Delivered-To: freebsd-security@freebsd.org Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by hub.freebsd.org (Postfix) with ESMTP id 38C7C37B400 for ; Thu, 7 Mar 2002 13:19:50 -0800 (PST) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.11.6/8.11.3) with ESMTP id g27LJnG12274 for ; Thu, 7 Mar 2002 15:19:49 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200203072119.g27LJnG12274@dc.cis.okstate.edu> To: freebsd-security@FreeBSD.ORG Subject: Re: Patched openssh Date: Thu, 07 Mar 2002 15:19:49 -0600 From: Martin McCormick Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Jacques A. Vidrine" writes: >Did you remove /usr/ports before extracting ports.tar.gz? No I did not. After you asked the question, I did and it appears that the build worked this time. I did see one warning at the end of the build which reported: gzip -cn /usr/ports/security/openssh/work/ssh/sftp/../sftp.1 > sftp.1.gz ===> scard uudecode /usr/ports/security/openssh/work/ssh/scard/Ssh.bin.uu Warning: Object directory not changed from original /usr/ports/security/openssh/work/ssh/scard That is the last line printed. This brings up another question. Why did leaving the old ports distribution ruin the new one? When you unpack a tar ball, any file with the same name as an older one clobbers the older file so the only things left from previous distributions would be files that aren't used in the new distribution so they certainly will waste space, but What could have hung around from the old stuff that polluted the new build? Should the new sshd work with the same old keys we are now using? I have a bunch of automated processes that would at least temporarily break if I had to remake keys or the system key changed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message