-
Notifications
You must be signed in to change notification settings - Fork 94
OSXfuse's SSHFS ignores remote group permissions ? #1
Comments
Macfusion comes with its own custom SSHFS binary, that seems to ignore the user's gid. It resides in Macfusion's application bundle. That's why sshfs is not in your path. It took some time, but earlier today I uploaded an official OSXFUSE SSHFS 2.3.0 package containing a universal To make Macfusion use OSXFUSE's SSHFS run the following commands in Terminal (assuming Macfusion is in your Applications folder):
To revert the changes run:
Please re-open the issue, if this does not work for you. |
Hello @bfleischer, thanks for your feedback ! Unfortunately, after installing the pkg and running the commands, it still does not work, permissions are wrong :-/ ls -alh /Volumes/remote_mount/folder/ ls: : Permission denied On the other hand, doing a regular ssh machine ls -alh folder/ works without problems. Here's some information on the sshfs I'm using from today: :Resources roman$ sshfs -V SSHFS version 2.3 (OSXFUSE SSHFS 2.3.0) OSXFUSE library version: FUSE 2.7.3 / OSXFUSE 2.3.4 no mount point :Resources roman$ which sshfs /usr/local/bin/sshfs :Resources roman$ ls -lah /usr/local/bin/sshfs -rwxr-xr-x 1 root wheel 5,5M 22 Jan 12:39 /usr/local/bin/sshfs |
I took a closer look at your first post and am now able to reproduce the issue. There is an important difference between regular SSH and SSHFS:
SSHFS tries to be smart and matches your remote user's uid/gid with your local user's uid/gid. This suffices in most cases but in your case your remote user just belongs to Here is how to fix this: You need to call sshfs with the option If you call sshfs from command line just add |
BTW: You are still using OSXFUSE 2.3.4. Version 2.3.8 has been release about a month ago and fixes some race conditions that might lead to deadlocks. You might want to upgrade :-) |
Yeah, that did the trick, thanks ! :D I've to define that -o flag for each mount point... Even if it's a minor issue, I would expect it to be a global setting instead (or as well). On top of that, would it make sense to have it as default setting for macfusion ? I think it's reasonable to have it as per the principle of least surprise (http://en.wikipedia.org/wiki/Principle_of_least_astonishment). Thanks for the hints... I'll upgrade as well, thanks for telling ! |
I encountered the same issue with FTP mount points .. but obviously the is no "ssh option" to set to do the trick .. any idea? Thank you |
I'm mounting it together with macfusion. Unless I own the remote files via the remote user, I cannot access the files via standard remote UNIX permissions. For example, I have access to this directory on the remote server via osxfuse:
But not this one, which I don't own by user, only by group. I'm able to access the files when logged in via regular interactive ssh though:
Is there any flag I can use to correct this ? I've also observed that sshfs is not on my path when I try to invoque it locally after installing OSXFUSE with macfuse backwards compatibility option checked.
Thanks for the fork guys, good work !
The text was updated successfully, but these errors were encountered: