Repository navigation
Please publish macOS .pkg for SSHFS 3.7.6 #389
Description
Thank you for the 3.7.6 release and the security fixes.
Could you please publish the macOS installer package, sshfs-3.7.6.pkg, as a release asset—consistent with 3.7.5 and earlier releases?
Homebrew’s sshfs-mac cask discovers versions only when a release contains an asset matching sshfs-<version>.pkg. Without the package asset, it remains on 3.7.5 and cannot update users to 3.7.6:
https://github.com/Homebrew/homebrew-cask/blob/HEAD/Casks/s/sshfs-mac.rb
If omission was intentional, could you clarify the recommended macOS distribution path for this release?
Metadata
Metadata
Assignees
Labels
No labels
Activity
abhinavagarwal07 commentedon Oct 22, 2026
Thanks for bringing this up. I am checking on this.
h4sh5 commentedon Oct 22, 2026
@bfleischer Hi can you please make a mac .pkg for this release?
bfleischer commentedon Oct 23, 2026
I'm not sure what the current status is, but as far as I remember, READDIR in SSHFS 3.x does not (or did not) support
rewinddir(3), effectively "violating" the FUSE contract. While this does not appear to be an issue on Linux, it causes problems on macOS and has resulted in numerous tickets being opened by SSHFS users in the macFUSE issue tracker.In my opinion, this issue should be addressed before proceeding with a release. Releasing a build with a known issue of this kind does not feel right. I know the issue has been raised in the SSHFS issue tracker, but I haven't been able to follow its progress closely because I've been very busy with macFUSE.
As a side note, SSHFS 2.x works perfectly fine and correctly supports
rewinddir(3).agross commentedon Oct 23, 2026
sshfs 3.7.5 didn’t have this issue?
bfleischer commentedon Oct 23, 2026
@agross 3.7.5 is affected as well.
agross commentedon Oct 23, 2026
Thanks for clarifying. If 3.7.5 has the same issue and received a macOS package, could you help me understand what makes it a blocker for packaging 3.7.6? From a user’s perspective, staying on 3.7.5 leaves the same issue in place while missing the security fixes in 3.7.6.
abhinavagarwal07 commentedon Oct 23, 2026
I have a fix for this ready #392 if someone wants to review.