On Thursday 17 January 2008, Ilya N. Golubev wrote: > With my system, with `kernel-2.6.17-1.2142_FC4', `glibc-2.3.6-3', > `e2fsprogs-1.37-4', the command: > > ./mount -nv -t iso9660 -o ro,norock,mode=0400,uid=ID_OF_REGULAR_USER DEVICE > DIR > > yielded the same results: `mode=' is honored in permissions of regular > files and ignored in ones of directories, leaving the latter too wide. > Agree that should clarify initial bug report this way. And it may be > inacceptable to let anyone read (or even search) mounted directories > for exactly the same reasons that call for not permitting to read file > data. this is a kernel issue then i think. mount just passes your arguments to the kernel. this dir/file difference is already reflected in the manpage where it says "mode" affects only files. you should file a bug in the kernel bugzilla: http://bugzilla.kernel.org/ -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
