I unchecked the 'security vulnerability' flag because in my testing, it doesn't actually allow more permissions to the user, it just looks like it will.
That is, this is a display issue only. fuse's umask seems to only affect the display of the bits, it doesn't actually change them. Thus, this bug is two-fold. We can apply the patch to fix the display issue (that is, use of umask will *look* like it works, rather than now, where it looks like all hell broke loose). But the underlying problem that umask doesn't seem to actually do anything (in terms of changing permissions to read/write) also should be addressed, otherwise what's the point? ** This bug is no longer flagged as a security vulnerability -- fuse does not handle umask correctly https://bugs.launchpad.net/bugs/239792 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
