You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device: redmi k20(davinci)
Android version: 14
Magisk version name: 47cc532
Magisk version code: 28101
When I only need systemless hosts, I do not need to give access to any third party apps. So I set "Superuser Access" to "disabled", and zygisk disabled. I expect that /system/bin/magisk will not mount at all, as this is only for convenience to 3rd party apps.
But the actual result is that it is mounted there.
Is it possible to not mount '/system/bin/' at all if "Superuser Access=disabled"?
The text was updated successfully, but these errors were encountered:
As for the communication between daemon and magisk_app, maybe we can implement some kind of inversion of control: instead of app connect to /debug_ramdisk/.magisk/device/socket, app can listen for a Unix socket under private directory, and magisk daemon connect to it.
As for the communication between daemon and magisk_app, maybe we can implement some kind of inversion of control: instead of app connect to /debug_ramdisk/.magisk/device/socket, app can listen for a Unix socket under private directory, and magisk daemon connect to it.
Alternatively, magisk could implement some kind of pcap on localhost udp port-range, similar to fwknop. User app can send handshake information to a port range, then magisk_daemon can answer back.
Device: redmi k20(davinci)
Android version: 14
Magisk version name: 47cc532
Magisk version code: 28101
When I only need systemless hosts, I do not need to give access to any third party apps. So I set "Superuser Access" to "disabled", and zygisk disabled. I expect that /system/bin/magisk will not mount at all, as this is only for convenience to 3rd party apps.
But the actual result is that it is mounted there.
Is it possible to not mount '/system/bin/' at all if "Superuser Access=disabled"?
The text was updated successfully, but these errors were encountered: