From owner-freebsd-current Sat Sep 22 11:42:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 2AD2F37B41A; Sat, 22 Sep 2001 11:42:45 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.6/8.11.6) id f8MIgiY88604; Sat, 22 Sep 2001 22:42:44 +0400 (MSD) (envelope-from ache) Date: Sat, 22 Sep 2001 22:42:43 +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: <20010922224243.A88511@nagual.pp.ru> References: <20010922151116.A82718@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i Sender: owner-freebsd-current@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 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? If this bug not present in very recent -current, I prever very recent login_cap merge into each branch instead of simple disabling. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message