d0b044a31d
This commit removes the "Rooted" mount namespace state, as it wouldn't fit in the categories made by root implementations. The three major root implementations divide apps into three categories: SU, Umounted, (with) Mounts. The SU one consists of apps that are allowed to elevate privileges, those don't have their mounts modified, and keep root mounts. As for Umounted, it consists of apps that will have root-related mounts umounted before being executed. And finally (with) mounts which are apps that although are not allowed to elevate privileges, still have the root-related mounts kept. Knowing that we can merge both SU and (with) Mounts into the same category: No modification to mounts/Keep root-related mounts. With that, "Mounts" mns state is also unmodified, compared to old "Modules" mns state. Those changes also reflect on the issue where new apps couldn't ask Magisk for root as they would have SU mount umounted, which now, as ReZygisk leave them unmodified, they can.
ReZygisk
简体中文|繁體中文|Bahasa Indonesia|Tiếng Việt|Português Brasileiro|Türkçe|French
ReZygisk is a fork of Zygisk Next, a standalone implementation of Zygisk, providing Zygisk API support for KernelSU, Magisk (besides built-in), and APatch (Work In Progress).
It aims to modernize and re-write the codebase to C (from C++ and Rust), allowing a more efficient and faster implementation of the Zygisk API with a more permissive license.
Note
This module/fork is WIP (Work In Progress); only use .zip from the Releases.
Although you may install the .zip from the Actions page, it is only at your discretion to install it since your device might enter bootloop.
Why?
The latest releases of Zygisk Next are not open-source, reserving entirely the code for its developers. Not only does that limit our ability to contribute to the project, but also impossibilities the audit of the code, which is a major security concern, as Zygisk Next is a module that runs with superuser (root) privileges, having access to the entire system.
The Zygisk Next developers are famous and trusted in the Android community, however, this doesn't mean that the code is not malicious or vulnerable. We (PerformanC) understand they have their reasons to keep the code closed-source, but we believe the contrary.
Advantages
- FOSS (Forever)
Dependencies
| Tool | Description |
|---|---|
Android NDK |
Native Development Kit for Android |
C++ Dependencies
| Dependency | Description |
|---|---|
lsplt |
Simple PLT Hook for Android |
Usage
We're currently in the process of cooking. (Coming Soon)
Installation
There are currently no available stable releases. (Coming Soon)
Translation
As of now, we don't have integration with another platform for translations but you may contribute to the add/new-webui branch. Please don't forget to include your GitHub profile in TRANSLATOR.md so that people can see your contribution.
Support
For any question related to ReZygisk or other PerformanC projects, feel free to join any of the following channels below:
- Discord Channel: PerformanC
- ReZygisk Telegram Channel: @rezygiskchat
- PerformanC Telegram Channel: @performancorg
Contribution
It is mandatory to follow PerformanC's Contribution Guidelines to contribute to ReZygisk. Following its Security Policy, Code of Conduct, and syntax standard.
License
ReZygisk is licensed majoritaly under GPL, by Dr-TSNG, but also AGPL 3.0, by The PerformanC Organization, for re-written code. You can read more about it on Open Source Initiative.