Skip to content

module: verify daemon SELinux startup and use BusyBox UID switching - #131

Draft
Leeestephen wants to merge 1 commit into
SuperTurtleDev:mainfrom
Leeestephen:fix/verified-module-startup
Draft

Leeestephen wants to merge 1 commit into
SuperTurtleDev:mainfrom
Leeestephen:fix/verified-module-startup

Conversation

@Leeestephen

Copy link
Copy Markdown
Collaborator

Summary

Android can read a retained daemon executable label before the custom SELinux
type becomes usable. During an Android 17 upgrade I observed the file label
look correct while the daemon still started in the broad KernelSU domain.

Probe the real transition boundedly, refresh the executable context after the
probe succeeds, launch the supported foreground daemon and verify its owned
PID/domain. Reject and reap failed children. Launch PulseAudio through KernelSU
BusyBox setuidgid so startup also works when Android su is unavailable.

Testing

Nine host fixtures pass for readiness, bounded retries, wrong-domain children,
label failure, probe cleanup and UID/GID launcher arguments. Shell syntax checks
pass. An earlier integrated version passed enforcing Android 17 cold boot on
alioth with BakaSU/ReSukiSU and a real Android audio sink.

Exact extracted-revision cold boot and other root-framework variants still
need validation. This branch is based directly on main and can be reviewed
independently of the OTA overlay guard in #130.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant