From owner-freebsd-security@FreeBSD.ORG  Tue Sep 14 14:32:51 2004
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 037A016A4CE; Tue, 14 Sep 2004 14:32:51 +0000 (GMT)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1C1E643D5D; Tue, 14 Sep 2004 14:32:46 +0000 (GMT)
	(envelope-from dmitry@atlantis.dp.ua)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by smtp.atlantis.dp.ua (8.12.6p2/8.12.6) with ESMTP id i8EEWZes098231;
	Tue, 14 Sep 2004 17:32:35 +0300 (EEST)
	(envelope-from dmitry@atlantis.dp.ua)
Date: Tue, 14 Sep 2004 17:32:35 +0300 (EEST)
From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
To: Xin LI <delphij@frontfree.net>
In-Reply-To: <20040914141820.GA1728@frontfree.net>
Message-ID: <20040914172844.X96954@atlantis.atlantis.dp.ua>
References: <20040909133319.A41151@atlantis.atlantis.dp.ua>
	<20040914131723.GA63705@i2.informatik.rwth-aachen.de>
	<20040914141820.GA1728@frontfree.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: freebsd-security@freebsd.org
cc: Volker Stolz <vs@freebsd.org>
Subject: Re: multiple vulnerabilities in the cvs server code
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2004 14:32:51 -0000

On Tue, 14 Sep 2004, Xin LI wrote:
>> Also, it would be nice if such an advisories advance kern.osreldate,
>> so auditfile could check this automatically; e.g., I have 4.9-RELEASE-p11,
>> which isn't vulnerable to this problem, but kern.osreldate is still 490000
>> there. If Security Officer bumps src/sys/conf/newvers.sh, why he doesn't
>> bump src/sys/sys/param.h?
>
> I think it is not applicable to bump param.h, as it represents an ABI change,
> which a security update should not introduce.  (just my $0.02 :-)

  Then it should be another possibility to get release "patch level" - maybe
by parsing kern.osrelease? In any case, it would be nice to add such a 
check, so portaudit won't complain when base system isn't vulnerable.

Sincerely, Dmitry
-- 
Atlantis ISP, System Administrator
e-mail:  dmitry@atlantis.dp.ua
nic-hdl: LYNX-RIPE