From owner-freebsd-hackers Sat Jan 1 15:39:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 9DB3814C4B for ; Sat, 1 Jan 2000 15:39:20 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id RAA30322 for hackers@freebsd.org; Sat, 1 Jan 2000 17:39:07 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200001012339.RAA30322@celery.dragondata.com> Subject: No 'stupid user tricks' filenames? To: hackers@freebsd.org Date: Sat, 1 Jan 2000 17:39:07 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone thought about a sysctl to disallow the creation/renaming of file names to make them contain characters they probably shouldn't have? While I have no idea why, my customers seem to enjoy finding filenames that will make afio choke, or make some tool somewhere not like them. Before I go about trying to implement this, does anyone have suggestions or comments? (Yes, I realize the tools should be able to handle things like this, and that I should cluebat anyone trying this. However, it's still annoying, and should probably be not allowed under secure environments) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message