Starting with the 4.0.0 release, redistributions bundled with commercial software are not allowed without specific prior written permission. However, osxfuse is update to 4.0.5 which supports both Big Sur and M1 macs, but with a caveat, The license has changed.
In Google Drive for desktop 45.0.12.0 dfsfuse version is 3.7.8 I believe, which as per the osxfuse release logs does not support Big Sur or even M1 macs. This is just my observation, but I think the issue with GDFS or GDfD or whatever the hell Google names it now is an issue with the dfsfuse version (a fork of the osxfuse project). I've reached out to our Google support rep to see if there's something more to it than the vague "supports Big Sur" in the GDFS changelog from October's version update, they probably have better avenues for support than anything we'd get as the customer but odds are it just doesn't actually support System Extensions yet like a lot of other apps we're encountering during testing. Our existing Kernel Extension config profile as well as the System Extension policy we're testing for GDFS have "allow users to approve kernel extensions" enabled but in both cases it does not work on Big Sur, an admin still must manually provide credentials to approve installation.
But after approval no system extension is actually registered with the system (but the app works). Even when installing the app on an intel macbook with Big Sur without JAMF, users are being prompted to approve a system extension for GDFS, not a kernel extension (unless the apple dialogue box is a liar which is very possible). That's unfortunately not the behavior we're seeing.
0 kommentar(er)
