From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gh0-f174.google.com ([209.85.160.174]:52490 "EHLO mail-gh0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755305Ab2FZS20 convert rfc822-to-8bit (ORCPT ); Tue, 26 Jun 2012 14:28:26 -0400 Received: by ghrr11 with SMTP id r11so238648ghr.19 for ; Tue, 26 Jun 2012 11:28:25 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 26 Jun 2012 11:28:23 -0700 Message-ID: Subject: Re: System Policy for Filenames From: Aaron Peterson To: linux-btrfs@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Billy, Thank you! I will look into FUSE. Ultimately, I want my / to be mounted with these rules,  I will need a boot loader to be able to handle it. I am wondering if filesystem software has hooks for AppArmor or SELinux, or some other Linux Security Module would be appropriated to add to filesystem code? Also, I tried joining a linux-fsdev mailing list, but it appears to be defunct. Oh, This is interesting: http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html -AP > > > On Tue, Jun 26, 2012 at 11:03 AM, Billy Crook wrote: >> On Fri, Jun 22, 2012 at 4:06 AM, Aaron Peterson >> wrote: >>>  I would like to make a system policy that restricts the characters >>> used in a filename, tests filenames by regular expression, and >>> enforces case-insensitive-compatible exclusivity. >>> >>> Where should I start? >> >> I would find a filesystem-agnostic mailinglist.  None of these >> objectives appear to have anything to do with btrfs.  There is >> probably a generic fs layer that would be the appropriate place for >> this, if not FUSE. >> >> You might also consider forcing users to access the fs through SAMBA >> which has similar capabilities already.