From owner-freebsd-questions  Fri Nov 22 11:30:19 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA11977
          for questions-outgoing; Fri, 22 Nov 1996 11:30:19 -0800 (PST)
Received: from localhost.my.domain (caliban.mrtc.org [199.4.33.251])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA11965
          for <questions@freebsd.org>; Fri, 22 Nov 1996 11:30:11 -0800 (PST)
Received: (from langfod@localhost) by localhost.my.domain (8.8.2/8.6.9) id JAA01080 for questions@freebsd.org; Fri, 22 Nov 1996 09:30:24 -1000 (HST)
Message-Id: <199611221930.JAA01080@localhost.my.domain>
Subject: Keeping users from bind'ing to ports
To: questions@freebsd.org
Date: Fri, 22 Nov 1996 09:30:24 -1000 (HST)
From: "David Langford" <langfod@dihelix.com>
X-blank-line: This space intentionaly left blank.
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Is there a way of keeping some users from being able to run programs
that bind to ports over 1024? (i.e. to keep users from running servers)

Ideally this would involve a user file like crontab uses to allow
known users to use the ports.


Thanks,
-David Langford
 langfod@dihelix.com