![]() The VFS kernel API that macFUSE relies on, is sill the only way to develop full-featured file systems for macOS. They are only removing the private kernel extension from macOS that was used by Microsoft and Dropbox. Apple did not deprecate the virtual file system kernel extensions in macOS 12.3. They have been using a private framework (including a kernel extension developed by Apple) that Apple made available to these two companies exclusively some time ago. (85890896)” Microsoft and Dropbox are not shipping their own kernel extensions. Both service providers have replacements for this functionality Dropbox is currently in beta. In the macOS 12.3 beta release notes Apple states: “The kernel extensions used by Dropbox Desktop Application and Microsoft OneDrive are no longer available. In issue #503, you discussed Apple-provided APIs which might allow macFUSE to become a userspace application, and said they weren't ready.Is Resilio’s Transparent Selective Sync still working with macOS 12 Monterey? I wonder if there are solutions to the problem now. Going back to what you said about macOS being closed source too, yes, this is true, but Apple has a security team auditing their source code and as far as we know, you are the only one managing the security of the macFUSE source code. This makes macFUSE a high-value target for state-backed and unaffiliated attackers because it has ring 0 access to machines containing sensitive data. What I am concerned about, though, are the security implications of making a kernel extension closed source.Ĭonsider that VeraCrypt is used by a number of government organizations and companies around the world for securing important data, and that VeraCrypt on Mac requires macFUSE to be installed to function. The kind of trust you discussed, though, is something I think you deserve because you have been diligently maintaining the project for a long time. You responded that it is up to users to decide whether to trust you, and that a lot of macOS and iOS are closed source also, yet we still put up with them. You and talked about trust, specifically how users can trust their installations of osxfuse when you took the code closed source. The point you (Benjamin) got across was that you should be compensated for your work, because without compensation to you the project would be unsustainable. ![]() In issue #841, there was a discussion about having a closed source project and what that means for the security of end users. Then I'll dump it (at least for the purpose I've been using it for). ![]() The MBP8,1 is somewhat special in this line, because it is the only Mac that doesn't support metal and has Monterey installed. There I get the message, that everything went well. Version available to install: 4.2.5." (which I had installed again using the installer. And the macFUSE preference pane shows: "FUSE does not appear to be installed. Now Cryptomator can't open the vaults anymore. Neither MBP8,1 (Late 2011), i5, Mon OCLP did act up - until macOS 12.4. On all of these machines, I have no issues with macFUSE. Thanks for the great work you do! Cryptomator in combination with macFUSE works great - on almost all of our Macs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |