Closed GoogleCodeExporter closed 9 years ago
First off, sshfs (or SFTP for that matter) doesn't do groups. At best, it can
try to detect the default remote gid
of the user who's making that SFTP connection (that is, mounting the volume).
This isn't a feature/misfeature
of sshfs itself--it's just that this can't be done (within reason) using the
means sshfs has.
Since sshfs doesn't have an file access authorization function of its own, it's
up to the local kernel (MacFUSE) to
authorize. The local kernel doesn't have all the remote information (what
groups you're a member of on the
remote machine, etc.) Therefore, even though you may expect to be able to read
files in that directory, that's
not how it works with sshfs. The underlying protocol isn't a full blown file
sharing protocol.
One "solution" would be to turn off local authorization altogether and defer
such decisions to "whatever
happens when you actually try to read/write/etc. through SFTP". This way, the
local kernel will never stop you
from accessing anything, even if based on permissions or ACLs it looks like you
can't access something. The
'defer_permissions' option enables this mode of operation in the next release
of MacFUSE.
This has been discussed before.
Original comment by si...@gmail.com
on 29 Oct 2007 at 2:36
Thanks. I searched the forum as best I could before posting, but couldn't find a
prior discussion.
I'll keep an eye out for the next release of MacFUSE.
Original comment by Boodl...@gmail.com
on 29 Oct 2007 at 3:41
Original issue reported on code.google.com by
Boodl...@gmail.com
on 29 Oct 2007 at 2:27