From owner-freebsd-current@FreeBSD.ORG Thu Apr 1 08:04:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BE4416A4CE; Thu, 1 Apr 2004 08:04:39 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C38CB43D41; Thu, 1 Apr 2004 08:04:38 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i31G4ZTv003419; Thu, 1 Apr 2004 20:04:35 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i31G4ZJg003418; Thu, 1 Apr 2004 20:04:35 +0400 (MSD) (envelope-from ache) Date: Thu, 1 Apr 2004 20:04:31 +0400 From: Andrey Chernov To: "Jacques A. Vidrine" , current@FreeBSD.org Message-ID: <20040401160429.GA3346@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , "Jacques A. Vidrine" , current@freebsd.org References: <20040331133132.GA2106@nagual.pp.ru> <20040331183921.GA14949@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040331183921.GA14949@madman.celabo.org> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.24.0.7; VDF 6.24.0.76 (host: pobrecita.freebsd.ru) Subject: Re: Last NSS commit is very dangerous X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2004 16:04:39 -0000 On Wed, Mar 31, 2004 at 12:39:21PM -0600, Jacques A. Vidrine wrote: > I'd really like DETAILS from anyone else encountering any difficulties > after yesterday's NSS commit. I have so far been unable to reproduce > the issue, nor has the patch submitter been able to reproduce it. I found exact reason (which also explain why nobody still not been hitted). Somehow while editing my /etc/nsswitch.conf access mode becomes 0600 while owned by root, i.e. no access from user programs. It immediately case bugs I describe. But previous NSS variant can handle this unreadable /etc/nsswitch.conf nicely, probably using defaults. I think new variant should be fixed to do the same. Unreadable /etc/nsswitch.conf is not enough reason to stop working. -- Andrey Chernov | http://ache.pp.ru/