From owner-freebsd-bugs Thu Oct 11 8:50:10 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 280A137B407 for ; Thu, 11 Oct 2001 08:50:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9BFo2261020; Thu, 11 Oct 2001 08:50:02 -0700 (PDT) (envelope-from gnats) Date: Thu, 11 Oct 2001 08:50:02 -0700 (PDT) Message-Id: <200110111550.f9BFo2261020@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Yar Tikhiy" Subject: Re: bin/19755: nologin not configurable Reply-To: "Yar Tikhiy" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/19755; it has been noted by GNATS. From: "Yar Tikhiy" To: , Cc: Subject: Re: bin/19755: nologin not configurable Date: Thu, 11 Oct 2001 19:41:11 +0400 First, your solution is by no means secure. Think what would happen if a user linked its ~/.nologin to /etc/master.passwd. Second, have you ever heard of term "creeping featurism"? See http://www.tuxedo.org/~esr/jargon/html/entry/creeping-featurism.html Sorry, but a standard operating system distribution doesn't need to meet your every whim. There are administration tasks that are specific to your site, that you have to do by yourself. Please also take a look at login.access(5). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message