From owner-cvs-all Thu Aug 27 10:14:29 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12289 for cvs-all-outgoing; Thu, 27 Aug 1998 10:14:29 -0700 (PDT) (envelope-from owner-cvs-all) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12237 for ; Thu, 27 Aug 1998 10:14:10 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id KAA15609; Thu, 27 Aug 1998 10:13:06 -0700 (PDT) Date: Thu, 27 Aug 1998 10:13:06 -0700 (PDT) From: Chris Timmons To: Matthew Dillon cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/ping ping.8 ping.c In-Reply-To: <199808271624.JAA14693@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It wouldn't have to be application specific so much as providing a facility to let applications discover whether a user belongs to a class which requires conservative restrictions for a particular environment (eg. isp-shell-account.) Let each application decide what if anything the presence or absence of such an attribute means. I do not believe it is in the interest of FreeBSD to hard-wire restrictions into common tools that make them cumbersome to use or subtract usefulness. -Chris On Thu, 27 Aug 1998, Matthew Dillon wrote: > I really don't think login.conf is the place to put application-specific > restrictions. > > -Matt