From owner-freebsd-security Sat Sep 22 11:58:35 2001 Delivered-To: freebsd-security@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id CC59B37B41C; Sat, 22 Sep 2001 11:58:22 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.6/8.11.6) id f8MIwLL88872; Sat, 22 Sep 2001 22:58:21 +0400 (MSD) (envelope-from ache) Date: Sat, 22 Sep 2001 22:58:21 +0400 From: "Andrey A. Chernov" To: Robert Watson Cc: security@FreeBSD.org, current@FreeBSD.org, developers@FreeBSD.org, security-officer@FreeBSD.org Subject: Re: ~/.login_conf disabling exact reasons wanted Message-ID: <20010922225821.A88800@nagual.pp.ru> References: <20010922151116.A82718@nagual.pp.ru> <20010922224243.A88511@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010922224243.A88511@nagual.pp.ru> User-Agent: Mutt/1.3.21i 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 On Sat, Sep 22, 2001 at 22:42:43 +0400, Andrey A. Chernov wrote: > On Sat, Sep 22, 2001 at 13:53:02 -0400, Robert Watson wrote: > > is at best unhelpful, and more likely quite harmful. It was verified by a > > number of FreeBSD developers on many of past releases, and on 4.4-RC, as > > well as FreeBSD 5.0-CURRENT. The patch was tested on many of those > > I test in on my current -current changing "copyright" and "welcome" to > various values and using "default" and "standard" and "me" but can't > reproduce this bug. Please tell me EXACT how you test in in -current. > > To be double sure, you can check out very recent -current libutil and try > it temporary moving your libutil out of the way. > > Could anybody else confirm this bug persent on very recent -current or not > present? Sorry for all that buzz, I am finally able to reproduce it on -current. I can't do it previously simple because I don't have empty login class field in /etc/passwd. This happens only with empty class field in passwd and "default" class in ~/.login_conf. This is NOT the way LOGIN_CAP supposed to work. It supposed to work as I describe in previous messages. I'll work on the proper fix tomorrow. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message