imanolbarba / diskarbitrator Goto Github PK

There aren't any. That needs to change

And contbuild with Actions

Title says all.

Seems to be an issue even in the old Disk Arbitrator.

As it is right now, when ejecting the disk we can know that it is an APFS container, but it doesn't seem obvious how to figure out from which device it came from.

Less ideally, we could assume that it's the device with the previous numeration (e.g disk4 if container is disk5), but I'm not excited about assuming things, so this needs some thinking through

There's nothing there!

It would be cool to have a "monitor" mode, where diskarbitratord logs any attempts to mount disks and then:

• if subscribed, clients get a notification, and they can then prompt the user and accept/deny the mount
• if not subscribed, clients can request a log of the events (we would also need to start storing logs in this scenario)

When a mount request is intercepted and forced read-only, we basically reject the existing request and create a new request with readonly flag.

However, any original mount options are lost, and there appears to be no way within the realm of possibility of DiskArbitration framework right now to obtain them.

Opening this issue for tracking