Reading past 's post, it looks like disabling SIP, whether temporarily or permanently, is not required. I am now able to use Cryptomator (which depends on macFUSE) without issue.
#MACFUSE SYSTEM EXTENSION BLOCKED INSTALL#
I did disable it temporarily to install macFUSE and work through steps 11-14. Just to be clear, SIP is not disabled permanently. Worked for me on macOS 12.1 and macFUSE 4.2.4 on an Intel-based mac from 2017 recently upgraded to 12.1 without a clean install. If you are highly pessimistic you could skip straight to step 8, but only a small (but significant) number of cases seem to need such extreme measures, so try the first steps first.
restart macOS (without enabling System Integrity Protection).install macFUSE (while System Integrity Protection is disabled).
restart macOS (as part of that process).IF you STILL get the error "System Extension Blocked".attempt once more to mount your filesystem.IF you get the error "System Extension Blocked".
#MACFUSE SYSTEM EXTENSION BLOCKED SOFTWARE#
attempt to mount your filesystem (using whatever software you have that relies on macFUSE).So the prevailing instructions coming from this thread seem to be: Is there a better way to test macfuse independent of sshfs? I tried running /Library/Filesystems/macfuse.fs/Contents/Resources/load_macfuse echo $?, which returns 1, indicating that the macfuse cannot be loaded, which makes me believe the issue is not related to sshfs. Have you checked in to see if your problem is mentioned there? Or if it's related to the specific command-line that you are calling in sshfs? If this issue only occurs with sshfs, perhaps it might be better to raise it there instead? Is your mac managed by a company who might have locked something down?
Are there any side issues mentioned in there that might apply to you? Everyone else in this thread using macFUSE 4.2.0 on macOS 11.5 seems to find the reboot fixes their issue, so we need to find out what is different in your case.Īlthough no-one here says they are using sshfs, recent comments in issue #705 say that sshfs users got things working with 4.2.0 on Big Sur.
0 kommentar(er)
