@[email protected] what makes you think macOS maintains a stable in-kernel API? 😬
@siguza @marcan Is apple continuously breaking the interfaces used by Kexts ?
@Sobex @siguza @[email protected] Apple looks like they are increasingly close to removing support for them.

@jaduncan @Sobex @[email protected] I guess on x86_64 they keep some level of compatibility.

But on arm64, they don't care. The entire arm64e ABI isn't even stable. Maybe PAC works differently on the next beta, good luck lol. Also, this page states that support for non-Apple kexts *will* be removed:

https://support.apple.com/en-gb/guide/security/sec7d92dc49f/web

Startup Disk security policy control for a Mac with Apple silicon

To set security policy on a Mac with Apple silicon, Startup Disk has replaced Startup Security Utility.

Apple Support
@siguza @Sobex @[email protected] Yes. I've wondered if they will do anything to make MacFUSE and NTFS drivers possible before removing them, but it would be very Apple not to do so to increase ecosystem lock-in.
@jaduncan @Sobex they've had "lifs" for a while now, and while it requires an antitlement to use, I vaguely recall someone being able to interface with it through some command line util by providing a URL-like string...? But of course that's not much use as long as it's not a documented, public API...

@siguza @Sobex Yeah. My assumption is that if some replacement happens formally it will happen because Paragon complain repeatedly about having their file system driver business nuked. My concern is more that any stable API might be accessed via a special developer approval cert from Apple. It's why I think differently about Paragon and MacFUSE - Paragon can sign the agreement and pay the protection money.

And if it is protection money then Paragon themselves will demand it's locked down.

@jaduncan @siguza @Sobex @marcan My understanding is the current recommendation is to use NFS