[MacPorts] #57676: sshfs 2.x unable to create mount points (Sierra/High Sierra and later)

MacPorts noreply at macports.org
Sun Nov 25 22:52:21 UTC 2018


#57676: sshfs 2.x unable to create mount points (Sierra/High Sierra and later)
-------------------------------+--------------------
  Reporter:  matt-hammond-bbc  |      Owner:  (none)
      Type:  update            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.5.4
Resolution:                    |   Keywords:
      Port:  sshfs             |
-------------------------------+--------------------
Description changed by matt-hammond-bbc:

Old description:

> 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:
> https://derflounder.wordpress.com/2016/09/21/macos-sierras-volumes-
> folder-is-no-longer-world-writable/
>
> 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.
>
>  * Original issue raised for osxfuse:
> https://github.com/osxfuse/osxfuse/issues/306
>  * Issue for sshfs: https://github.com/osxfuse/sshfs/issues/27
>  * The change to sshfs 3.x:
> https://github.com/libfuse/sshfs/commit/861d308a03319e23286290ee8cffc6fd307e0ec9
>

> Example:
> {{{
> $ sshfs user at SERVER:/ /Volumes/XXXX
> -oreconnect,volname="SERVERNAME",idmap=user
> mount: realpath /Volumes/XXXX: No such file or directory
> }}}

New description:

 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:
 https://derflounder.wordpress.com/2016/09/21/macos-sierras-volumes-folder-
 is-no-longer-world-writable/

 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.

  * Original issue raised for osxfuse:
 https://github.com/osxfuse/osxfuse/issues/306
  * Issue for sshfs: https://github.com/osxfuse/sshfs/issues/27
  * The change to sshfs 3.x:
 https://github.com/libfuse/sshfs/commit/861d308a03319e23286290ee8cffc6fd307e0ec9


 Example (running High Sierra 10.13.6 with:
  * sshfs @2.10_0
  * osxfuse @3.8.2_0
 {{{
 $ sshfs user at SERVER:/ /Volumes/XXXX
 -oreconnect,volname="SERVERNAME",idmap=user
 mount: realpath /Volumes/XXXX: No such file or directory
 }}}

--

-- 
Ticket URL: <https://trac.macports.org/ticket/57676#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list