From owner-freebsd-security@FreeBSD.ORG Wed Sep 17 17:38:44 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA93A16A4B3 for ; Wed, 17 Sep 2003 17:38:44 -0700 (PDT) Received: from mail.npubs.com (npubs.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7273443F3F for ; Wed, 17 Sep 2003 17:38:44 -0700 (PDT) (envelope-from nielsen@memberwebs.com) Resent-Message-Id: Message-ID: <3F68FE17.5050700@memberwebs.com> From: Nielsen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-security@freebsd.org X-Enigmail-Version: 0.81.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Resent-Date: Thu, 18 Sep 2003 08:50:26 +0000 (GMT) Resent-From: nielsen@memberwebs.com (Postfix Filters) Subject: ftp.freebsd.org out of date? (WRT security advisories) X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Thu, 18 Sep 2003 00:38:45 -0000 X-List-Received-Date: Thu, 18 Sep 2003 00:38:45 -0000 It seems (at least for me) the patches on ftp.freebsd.org are out of date for the 03:12 security advisory (openssh). ftp2.freebsd.org has them fine. I'm wondering if this is a mirror issue or perhaps round-robin DNS problem? What compounds the issue is that right now the old openssh 3.7 patches are there (on ftp.freebsd.org), but not the 3.7.1 patches (which can be found on ftp2.freebsd.org). This could conceivably cause someone to miss a patch. Am i doing something wrong? If not, then this is just a little heads up. Perhaps it would be better to include ftp2.freebsd.org links in the security advisories. Hate to complain. The FreeBSD security team has done a great job, especially in the midst of this whole openssh mess. Nate Nielsen