System Policy for Filenames

System Policy for Filenames

[Aaron Peterson]

Hello btrfs group:

 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 am trying to solve a few problems for my catproof Linux project.
* Compatibility with other systems.
* Protect users from   "-rf", or "*"  files that mess with shell
expansion and poorly written shell scripts.
* possibly ensure that I can type the filenames, and defend against
look-alike characters
(This would preferably just come up as a warning,  KDE converts a "/"
in a filename to a look-alike and broke my system, but I recognize
that I will need to access file names in multiple languages)


Thank you!

Re: System Policy for Filenames

[Aaron Peterson]

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 <billycrook@gmail.com> wrote:
>> On Fri, Jun 22, 2012 at 4:06 AM, Aaron Peterson
>> <myusualnickname@gmail.com> 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.

Re: System Policy for Filenames

[Fajar A. Nugraha]

On Wed, Jun 27, 2012 at 1:28 AM, Aaron Peterson
<myusualnickname@gmail.com> wrote:
> 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.

Try looking at how ubuntu live cd works. Last time I check, it can use
unionfs-fuse as "/" to make the read-only cd media appear "writable"
live session. Something similar should be applicable to your needs.

>  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?

Not that I know of.

-- 
Fajar