mukulyadav49 / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

default idmap doesn't work #177

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
"User and group ID mapping is now turned on by default. This means that 
user/group IDs of the 
user logging in to the remote (SSH) machine will be automatically translated to 
the user/group 
IDs of the local user."

This doesn't work for me; user/group is showing only the remote end, e.g. they 
don't match 
local, and I have no permissions. In further words, the "ls -l" of an 
sshfs-mounted dir shows 
numerical user/group IDs rather than my owner user/group. I'm using sshfs:

(Mac OS X 10.4.9, Intel, remote host is FreeBSD 4.x, remote is OpenSSH_3.5p1, 
local is 
OpenSSH_4.5p1.

% sshfs --version
SSHFS version 1.7
FUSE library version: 2.6.5
MacFUSE version 0.3.0
using FUSE kernel interface version 7.8

I have to explicitly set '-o idmap=user' to get just the user to map. I'd like 
to not have to do this, 
naturally. is this a bug, or is it the user's fault?

commandline:

% sshfs user@remote.host: /some/dir -o idmap=user,volname=remote.hostname

Original issue reported on code.google.com by jubal.ke...@gmail.com on 10 May 2007 at 1:40

GoogleCodeExporter commented 9 years ago
Where did you get the sshfs from? Did you compile it yourself? Did it come from 
fink? From MacPorts? From 
MacFusion? From some other independent distributor? If you got it from the 
MacFUSE site itself, are you sure 
you've upgraded *sshfs* to the latest?

It should say something like this:

% sshfs --version
SSHFS version 1.7 (MacFUSE, 10, May 4 2007, 15:04:35)
FUSE library version: 2.6.5
MacFUSE version 0.3.0
using FUSE kernel interface version 7.8

Original comment by si...@gmail.com on 10 May 2007 at 1:49

GoogleCodeExporter commented 9 years ago
jubal.kessler: unless you report otherwise, I'm assuming that your sshfs was 
not up-to-date, as is indicated by 
your version string. Feel free to provide more information if you're still 
seeing this problem.

Original comment by si...@gmail.com on 12 May 2007 at 12:47