From owner-freebsd-questions Wed Aug 7 7:23:10 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1804B37B400 for ; Wed, 7 Aug 2002 07:23:09 -0700 (PDT) Received: from iota.root-servers.ch (iota.root-servers.ch [193.41.193.195]) by mx1.FreeBSD.org (Postfix) with SMTP id D0FB543E8A for ; Wed, 7 Aug 2002 07:23:07 -0700 (PDT) (envelope-from gaml@buz.ch) Received: (qmail 27377 invoked from network); 7 Aug 2002 14:23:06 -0000 Received: from dclient217-162-128-229.hispeed.ch (HELO gaxp1800) (217.162.128.229) by 0 with SMTP; 7 Aug 2002 14:23:06 -0000 Date: Wed, 7 Aug 2002 16:23:38 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.60q) Educational Reply-To: Gabriel Ambuehl X-Priority: 3 (Normal) Message-ID: <18221229687.20020807162338@buz.ch> To: questions@freebsd.org Subject: Forcing umask values (i.e. stopping users from making files world accessible)? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm wondering whether there is any way to truly stop users (they have (s)FTP access, CGI, PHP) from making their scripts world accessible. I know that I could set umask 027 so that all new files are 750 by default but as far as I understand the umask concept, they still can call chmod and make the files world accessible again, right? So I'm looking for a bullet proof solution that really stops users from making their data world accessible. TIA & regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message