From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 14:28:04 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 4574716A4CE; Mon, 23 Feb 2004 14:28:04 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 283EC43D1D; Mon, 23 Feb 2004 14:28:04 -0800 (PST) (envelope-from tim@kientzle.com) Received: from kientzle.com (54.kientzle.com [66.166.149.54] (may be forged)) by kientzle.com (8.12.9/8.12.9) with ESMTP id i1NMPKkX094860; Mon, 23 Feb 2004 14:25:20 -0800 (PST) (envelope-from tim@kientzle.com) Message-ID: <403A7DD0.2090802@kientzle.com> Date: Mon, 23 Feb 2004 14:25:20 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <6.0.1.1.1.20040223171828.03de8b30@imap.sfu.ca> <200402231516.16586.jhb@FreeBSD.org> <403A64E7.4020607@kientzle.com> <200402231553.34677.jhb@FreeBSD.org> In-Reply-To: <200402231553.34677.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org cc: Colin Percival cc: kientzle@acm.org Subject: Re: What to do about nologin(8)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 22:28:04 -0000 John Baldwin wrote: > > My point (sigh) is that doing system("logger") has the same problem set as > making nologin dynamic ... No, it doesn't. Not if you make nologin static and have it create a fresh environment before running any external programs. This would also be considerably more compact than statically linking in the logging functions. > Also, personally, I would rather have nologin be static than fix the one > known case of login -p and just hope no other cases pop up in the future. > Call me paranoid. :) Armoring nologin(8) is insufficient. In particular, as David Schultz pointed out, there are a lot of home-grown nologin scripts out there that are potentially vulnerable regardless of what we do with the "official" nologin program. Tim Kientzle