Hallo,
The reason for this Fuse Bug was a simple Typo in the FuSE kernel Module...,
Becaus a local variable shdows a global one ....
Valient Gough [EMAIL PROTECTED] wrote at Sa 16.02.2008:
>The FUSE author (Miklos) has found the problem in the FUSE kernel
module. He has suggested the following fix:
>Index: linux-2.6.24/fs/fuse/dir.c
>===================================================================
>--- linux-2.6.24.orig/fs/fuse/dir.c 2008-02-10 18:40:19.000000000 +0100
>+++ linux-2.6.24/fs/fuse/dir.c 2008-02-15 10:20:27.000000000 +0100
>@@ -905,7 +905,7 @@ static int fuse_permission(struct inode
> }
> if (fc->flags & FUSE_DEFAULT_PERMISSIONS) {
>- int err = generic_permission(inode, mask, NULL);
>+ err = generic_permission(inode, mask, NULL);
>
> /* If permission is denied, try to refresh file
> attributes. This is also needed, because the root
>
>
>Thanks for the report!
So, this problem has been detected quick, and hopefully all further FuSE
Releases are
Error free concerning this bug
________________________________
Bernd Oelker
HSP GmbH
48149 Münster
Johann-Krane-Weg 21
Germany
Tel: +49 251 38424-0
Fax: +49 251 38424-20
Mobil: +49 171 75 67 674
Web: www.hspg.de
Web: www.hsp-translog.de
E-Mail: [EMAIL PROTECTED]
Sitz: Münster
Amtsgericht Münster HRB 2485
Geschäftsführung: Dipl.-Ing Klaus Hiesgen, Dipl.-Phys. Bernd Oelker
________________________________
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Chris Coulson
Gesendet: Montag, 14. Juli 2008 00:42
An: Bernd Oelker [HSP]
Betreff: [Bug 191831] Re: bash test -w (writeable) always SUCCEED on EncFS
+linux-2.6.24.X ?
Valient - This is a bug with the FUSE kernel module which is shipped
with the kernel, so it should be assigned to the kernel.
It also still exists, so I'm confirming. You might find this useful:
http://article.gmane.org/gmane.comp.file-systems.fuse.devel/5789
I discovered this bug because I am testing bindfs. I've created the
following bindfs mount in my fstab:
"bindfs#/home/.shared /home/shared fuse
owner=root,group=root,[EMAIL PROTECTED],perms=000:u+rwX:g+rX:o+rX
0 0"
Basically, /home/shared should only be writable by anybody belonging to the
group 'shared-rw'. /home/shared should be readable by everybody.
However, I find that any user can write to /home/shared, regardless of whether
they belong to the group 'shared-rw'.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
bash test -w (writeable) always SUCCEED on EncFS + linux-2.6.24.X ?
https://bugs.launchpad.net/bugs/191831
You received this bug notification because you are a direct subscriber of the
bug.
Status in Encrypted Filesystem for Linux: Invalid Status in "linux"
source package in Ubuntu: Confirmed
Bug description:
While putting a sourcecode Archiv tree on an encfs - Filesystem I recognised,
that my shell scripts which check if a file is writeable FAILED, because if [
-w $file ] then ... always results true (file shows on ls only readonly !)
Environment:
OpenSuSE 10.3, linux-2.6.24.2, FUSE 2.7.2 without kernel module, encfs-1.4.1.1
If I untar the same src - Code Archiv on an normal Reiserfs - Filesystem, if [
-w $file ] behaves normal. I "feel" it depends on an linux Kernel update,
because on a latest linux-2.6.23.X I reached the same.
If I edit this file via vi - Editor, it shows the readonly file correct as
readonly !
=> There must be an combination of Kernel, BASH, encfs which results in this
ERROR. My encfs - Filesystem ist mounted -public !
--
bash test -w (writeable) always SUCCEED on EncFS + linux-2.6.24.X ?
https://bugs.launchpad.net/bugs/191831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
