#45521: osxfuse 2.7.0 fails to load (Yosemite) ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Changes (by ryandesign@…): * keywords: => yosemite * owner: macports-tickets@… => dports@… -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#45521: osxfuse 2.7.0 fails to load (Yosemite) ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Comment (by macports.org@…): I do have an Apple developer certificate, but I ran into problems where my signature was valid, but not accepted by the system security assessment policy. The problem seems to be that not every developer certificate can be used to sign kernel extensions. This may prove to be a real problem for many (most) MacPorts users. Meanwhile, I have used the following workaround: 1. Install the upstream (i.e. "official") ''osxfuse'' binary from https://osxfuse.github.io/ that corresponds to what MacPorts is using. At the time of this writing, it is 2.7.0. 2. In the shell, replace the MacPorts ''osxfuse'' with the signed binary: {{{ $ cd /opt/local/Library/Filesystems $ sudo mv osxfusefs.fs osxfusefs.fs.macports $ sudo ln -s /Library/Filesystems/osxfusefs.fs osxfusefs.fs }}} Any port that has a dependency on /opt/local/Library/Filesystems/osxfusefs.fs/... should now work. I have tested successfully with ''encfs'' and ''TrueCrypt'' (the latter with a local portfile, see https://trac.macports.org/ticket/41421 for details). Maybe the cleanest solution is to modify the ''osxfuse'' port to download and install the upstream binaries? -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#45521: osxfuse 2.7.0 fails to load (Yosemite) ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Comment (by yszhou4tech@…): Replying to [comment:5 macports.org@…]:

I do have an Apple developer certificate, but I ran into problems where my signature was valid, but not accepted by the system security assessment policy. The problem seems to be that not every developer certificate can be used to sign kernel extensions. This may prove to be a real problem for many (most) MacPorts users.

Meanwhile, I have used the following workaround:

1. Install the upstream (i.e. "official") ''osxfuse'' binary from https://osxfuse.github.io/ that corresponds to what MacPorts is using. At the time of this writing, it is 2.7.0. 2. In the shell, replace the MacPorts ''osxfuse'' with the signed binary: {{{ $ cd /opt/local/Library/Filesystems $ sudo mv osxfusefs.fs osxfusefs.fs.macports $ sudo ln -s /Library/Filesystems/osxfusefs.fs osxfusefs.fs }}}

Any port that has a dependency on /opt/local/Library/Filesystems/osxfusefs.fs/... should now work.

I have tested successfully with ''encfs'' and ''TrueCrypt'' (the latter with a local portfile, see https://trac.macports.org/ticket/41421 for details).

Thanks for the tip. I may note that the osxfuse version must match what sshfs requires. As of this writing, it is 2.7.0, not the newest stable 2.7.2. Otherwise, the following error may appear when trying to use sshfs. {{{ this OSXFUSE library version is incompatible with the OSXFUSE kernel extension }}} Another glitch is that if sshfs or other filesystems that depend on osxfuse was installed later, the installation process may emit the following error, but the installation will still work without problem. {{{ ---> Activating sshfs @2.5_0 ---> Cleaning sshfs ---> Updating database of binaries ---> Scanning binaries for linking errors Warning: Error parsing file /opt/local/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext.dSYM/Contents/Resources/DWARF/osxfusefs: Error opening or reading file ---> No broken files found. }}}

Maybe the cleanest solution is to modify the ''osxfuse'' port to

download and install the upstream binaries? I agree :) -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

#45521: osxfuse fails to load on Yosemite due to unsigned kext ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: fixed | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Changes (by dports@…): * status: assigned => closed * resolution: => fixed Comment: Should be fixed in r129493. We are now installing the signed kext from the osxfuse dmg on Yosemite. -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:28> MacPorts <https://www.macports.org/> Ports system for OS X

#45521: osxfuse fails to load on Yosemite due to unsigned kext ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: fixed | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Comment (by fw@…): Replying to [comment:29 macosx12345@…]:

Replying to [comment:5 macports.org@…]:

...

Meanwhile, I have used the following workaround:

1. Install the upstream (i.e. "official") ''osxfuse'' binary from https://osxfuse.github.io/ that corresponds to what MacPorts is using. At the time of this writing, it is 2.7.0. 2. In the shell, replace the MacPorts ''osxfuse'' with the signed binary: {{{ $ cd /opt/local/Library/Filesystems $ sudo mv osxfusefs.fs osxfusefs.fs.macports $ sudo ln -s /Library/Filesystems/osxfusefs.fs osxfusefs.fs }}}

Any port that has a dependency on /opt/local/Library/Filesystems/osxfusefs.fs/... should now work.

Since an upgrade of osxfuse a couple of weeks ago, even under Mac OS 10.6.8 I got the same error message when trying to load osxfuse (```/opt/local/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext failed to load - (libkern/kext) not loadable (reason unspecified); check the system/kernel logs for errors or try kextutil(8). the OSXFUSE file system is not available (71)```). The workaround above solves the issue for me (with, at the time of this writing, the official 2.7.5 binary osxfuse and the port of osxfuse 2.7.5 installed). Thanks!

Therefore, I suggest extending the solution adopted in r129493 to Mac OS 10.6.

It's certainly not exactly the same issue, since 10.6 has no kext signing requirement. Perhaps there's something wrong with your build system that causes kexts to build incorrectly. You don't mention using kextutil to see what OSX was complaining about. -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:31> MacPorts <https://www.macports.org/> Ports system for OS X