Opened 2 years ago

Last modified 2 years ago

#57676 assigned update

sshfs 2.x unable to create mount points (Sierra/High Sierra and later)

Reported by: matt-hammond-bbc (Matt Hammond) Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc:
Port: sshfs

Description (last modified by matt-hammond-bbc (Matt Hammond))

A change in Mac OS Sierra and later has locked down permissions on /Volumes such that it is not possible to create mount points without root privileges. Request that this port be updated to sshfs 3.x to resolve this.

The security changes to Sierra and later:

osxfuse 3.5.0 added support to automatically create mount-points, but sshfs also needed changes to stop it checking that the mount-point already exists. This change has been made to the 3.x branch, but not the 2.x branch.

Example (running High Sierra 10.13.6 with:

  • sshfs @2.10_0
  • osxfuse @3.8.2_0
    $ sshfs user@SERVER:/ /Volumes/XXXX -oreconnect,volname="SERVERNAME",idmap=user
    mount: realpath /Volumes/XXXX: No such file or directory

Change History (4)

comment:1 Changed 2 years ago by matt-hammond-bbc (Matt Hammond)

Description: modified (diff)

comment:2 Changed 2 years ago by jmroot (Joshua Root)

Owner: set to drkp
Status: newassigned

comment:3 Changed 2 years ago by ra1nb0w

sshfs 2.10 contains the patch

In any case, I receive the following error if I use /Volume. Works flawless with ~/test directory

sshfs -p22 -d /Volumes/test
mount_osxfuse: /Volumes/test: Permission denied

If I understand correctly the new behaviour, osxfuse could create the mount-point in /Volume and use it. right?


macOS 10.14.3 18D109
Xcode 10.1 10B61
osxfuse @3.8.3_0
sshfs @2.10_0

comment:4 Changed 2 years ago by matt-hammond-bbc (Matt Hammond)

Yes, if I understand you correctly. The right version of Osxfuse will create the mount point. What is important is that sshf should not object if the mount point does not yet Exist.

Note: See TracTickets for help on using tickets.