From owner-freebsd-security@FreeBSD.ORG Tue Apr 30 22:48:54 2013 Return-Path: Delivered-To: freebsd-security@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 309204BC; Tue, 30 Apr 2013 22:48:54 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 047111DA9; Tue, 30 Apr 2013 22:48:54 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id C899D23F804; Tue, 30 Apr 2013 18:48:52 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us C899D23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 30 Apr 2013 18:48:50 -0400 From: Glen Barber To: Brett Glass Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <20130430224850.GA1579@glenbarber.us> References: <201304292055.r3TKtcEs039958@freefall.freebsd.org> <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us> <201304300416.WAA20729@lariat.net> <20130430042415.GG1588@glenbarber.us> <201304301936.NAA02519@lariat.net> <20130430211531.GA1621@glenbarber.us> <201304302241.QAA05359@lariat.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <201304302241.QAA05359@lariat.net> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-security@FreeBSD.org, Colin Percival , Chris Rees X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 22:48:54 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 30, 2013 at 04:41:03PM -0600, Brett Glass wrote: > At 03:15 PM 4/30/2013, Glen Barber wrote: >=20 > >Let's start from the beginning. What is the name of your custom kernel? >=20 > The file name of the compiled kernel? The file name of the configuration = file? > Or the identification string within the kernel? >=20 Yes. (All of them.) > The file name is, of course, /boot/kernel/kernel. It's built without > modules, so > it's the only file in the directory /boot/kernel. >=20 > The configuration file is at /sys/amd64/conf/GATEWAY. >=20 > The identification string within the kernel is GATEWAY. >=20 > I am not sure what you're driving at here, though, so please explain. >=20 What I was getting at is seeing if you had a custom kernel called GENERIC, despite the vast amounts of documentation noting that GENERIC should _not_ be modified to customize the kernel. So, since I know you're not new to FreeBSD, if you feel there is a bug somewhere, please file a PR. I disagree that there is a problem, however, since users building a custom kernel should _not_ use freebsd-update(8) for kernel upgrades. Glen --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRgEpSAAoJEFJPDDeguUajWz4H/jLPw4+qwDGL0olN1EDgr1U0 Y20jp4hiTul5pUaFff57sa71MhgPPpa3yiT/D3PaSf33eLyi+jkK9xcD1k1ShqZZ VneTPq382qFZTsPVi7eBGFxRr3Q6cvO8MfqPg/bbvQ7Yw1Dojul2z/rHLeVxW6SM 9aWPnht6ubVe/qVEEON30ggvkQk+sh6py42+eBszRWU2ozI7A9PsnmWkcgt2OjB7 5QIU8815dXrQBoI4cSlx9jMgSYGh5tkmpDWn89fMNzLyps0m9/FWT3hwnRzcQakZ ARt39VOClQ+HHq1/0kS1Sa4oUVSu8tQivUtR0dqsFWaAI8YjxzrMzjQJ0NCtn40= =hirH -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv--