Date: Sat, 22 Sep 2001 22:42:43 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Robert Watson <rwatson@FreeBSD.ORG> 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> In-Reply-To: <Pine.NEB.3.96L.1010922133112.39778A-100000@fledge.watson.org> References: <20010922151116.A82718@nagual.pp.ru> <Pine.NEB.3.96L.1010922133112.39778A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010922224243.A88511>