A new guide to understand better the umask management:
http://wiki.lapipaplena.org/index.php/How_to_mount_SFTP_accesses
(with special care with owners and permissions questions)
--
fuse does not handle umask correctly
https://bugs.launchpad.net/bugs/239792
You received this bug notification beca
Since upstream doesn't consider this to be a bug, I'm closing this
issue.
** Changed in: fuse (Ubuntu)
Status: Confirmed => Invalid
--
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, wh
I asked the fuse mailing list about this. Here is their answer
(interspersed with my initial email):
"""
> '-o umask=' seems to:
> (A) have an odd display bug because of a missing ampersand (see [1]) and
It's a feature not a bug. Notice, how other filesystems like msdos
also use -oumask mount o
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 b
** Changed in: fuse (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: fuse (Ubuntu)
Milestone: None => karmic-alpha-6
--
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
I see the behaviour using sshfs and umask=002, with no other option
passed to sshfs.
1) All remote files appear locally with incorrect permissions, most
annoyingly with the +x flag.
2) Touching files creates them remotely as 644 instead of 664.
--
fuse does not handle umask correctly
https://bu
The attached patch fixes the wrong displayed permission problem, but
does not fix the wrong creation flags. Setting the local umask to 002
too, besides being something I'd like to avoid, does not change the
behaviour.
--
fuse does not handle umask correctly
https://bugs.launchpad.net/bugs/239792
Thanks for taking the time to report this bug and helping to make Ubuntu
better. I don't see this behavior. What settings are you using, and on
what fuse filesystem type?
** Changed in: fuse (Ubuntu)
Status: New => Incomplete
--
fuse does not handle umask correctly
https://bugs.launchpa
** Visibility changed to: Public
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
