Re: chmod & chown don't work

From: Cheng Hong (hcheng_at_psl.com.sg)
Date: 12/31/04 

Date: Fri, 31 Dec 2004 10:09:20 +0800

Thanks. Now it is working fine. Just forgot that there is no security in
FAT32.

As also pointed out by Torfinn, changing the properties of the mount point
gave the the same effect.

cheers

Cheng

Dariusz Kuli?ski / TaKeDa wrote:

> On Thu, 30 Dec 2004 14:39:24 +0800, Cheng Hong wrote:
>
>> Hi all,
>>
>> Recently, I successfully mounted the FAT32 partition to my FreeBSD5.3
>> box. Now, the problem is that I can only work on it as root. The
>> directory created cannot be changed to allow other user's access. Anyone
>> has experience on this?
>
> What do you expect? FAT32 doesn't have any security settings. So you
> cannot change rights of individual files/directories. Only thing you can
> do is set rights on mount time:
>
> In man mount_msdosfs there are flags:
> | -u uid Set the owner of the files in the file system to uid. The
> | default owner is the owner of the directory on which the
> | file system is being mounted.
> |
> | -g gid Set the group of the files in the file system to gid. The
> | default group is the group of the directory on which the
> | file system is being mounted.
> |
> | -m mask
> | Specify the maximum file permissions for files in the file
> | sys-
> | tem. (For example, a mask of 755 specifies that, by
> | default, the owner should have read, write, and execute
> | permissions for files,
> | but others should only have read and execute permissions.
> | See
> | chmod(1) for more information about octal file modes. Only
> | the
> | nine low-order bits of mask are used. The value of -M is
> | used if
> | it is supplied and -m is omitted. The default mask is
> | taken from the directory on which the file system is being
> | mounted.
>
>
> For more info read man mount_msdosfs
>

Relevant Pages

  • Re: [patch 7/8] allow unprivileged mounts
    ... mounting of this filesystem may not constitute a security problem. ... is there any realistic likelihood that any filesystem ... If it worked for mount --bind for any fs I could see uses of this. ...
    (Linux-Kernel)
  • Re: RE²: FreeBSD isdangerous!
    ... > in my debian Linux partitions. ... The problem isn't specific to FreeBSD. ... partition from another fs is a security problem in your particular ... mount it, ...
    (freebsd-newbies)
  • Re: Can not migrate mailboxes from Exchange 2003 SP2 to Exchange 2007
    ... message also when I go to mount my public folder database. ... Exchange is unable to mount the database that you specified. ... You need to check the security on the OU in AD where the users are located. ... clicking on the user and choosing move mailbox. ...
    (microsoft.public.exchange.setup)
  • Re: [RFC][PATCH 4/11] security: AppArmor - Core access controls
    ... + * authorizes mask operations on pathname (due to lack of vfsmnt it is sadly ... later and your entire security system seems to be down the drain. ... If you are a confined process, then you don't get to mount things, for ... that does mount things as part of its legitimate purpose, ...
    (Linux-Kernel)
  • Re: /proc directory
    ... >> particularly concerned about security, in which case, you don't mount ... > procfs has been the source of numerous local root vulnerabilities over ...
    (freebsd-questions)