That was what I figured since it's relatively new. Unfortunately, because of this, I have been unable to get sshfs working in any meaningful way. Regardless of whether I run sshfs as root or as a regular user (with kern.usermount=1), I can't access any of the files. I don't see a way to change the user mapping or the umask with the fuse limitations you mention. Perhaps I'm missing something...?
This is easy for me to say since I have no idea how difficult it would be to implement, but this feature strikes me as something that would be highly useful, integrated as a core feature in OpenSSH. NFS strikes me as a ripe candidate for the OpenSMTPD/OpenNTPD/OpenHTTPD treatment. It is complicated, arcane, and requires several open ports. Integrated sshfs-like functionality in OpenSSH would seem to me to be a good NFS replacement. On Sun, Feb 14, 2016 at 1:40 PM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2016-02-12, Daniel Boyd <dan...@boydemail.com> wrote: > > I am having this same issue. I also tried adding the -d switch > > to see if that would shed any light. > > > > $ sshfs -d -o idmap=user ... > > command-line line 0: Bad number. > > remote host has disconnected > > > > $ sshfs -d -o idmap=file,uidfile=myuidfile,gidfile=mygidfile ... > > command-line line 0: Bad number. > > remote host has disconnected > > > > Any ideas? I'm also running 5.8. > > > > Thanks! > > Daniel > > > > > > iirc the option-parsing needs something from the OS that OpenBSD probably > doesn't > have (FUSE on OpenBSD is still missing some bits).
