Privacy + Secure Tech Corner Channel 🛡️
90 subscribers
6.66K photos
581 videos
542 files
16.2K links
Here you can find all about GSI's, ROM's, GKI Kernel's, Tech NEWS, Updates, Root methods, Magisk Module, Overlay's, Hacker things, FLOSS, FOSS, Privacy + Secure Stuff and many more!
Download Telegram
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
No deleted account found from 90 scanned users from this group 🚫👻

💬 Send /lang to change language of the bot
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from PerformanC (Pedro)
Recently, quite a lot of rather interesting commits were committed to ReZygisk. Some of those include quite big changes, and I'm here to information the community about the most memorable changes.

1. Full rewrite of the codebase

Since June 15th of 2024, our focus has been always two things: transparency, and the rewrite to C. While transparency had been achieved in the first button clicked, the rewrite was being performed slowly over time.

However, today, January 18th of 2026, we finally completed our goal, porting the last pieces of C++ code to C (while -release reduced 10kb only, debug reduced by 120kb!), finalizing and starting a new era on ReZygisk's development (and licensing state).

This will ensure a much more seamless development experience, and stability since we won't need to worry with messing C++ anymore.

2. Remote CSOLoader

Since the start, all Zygisk implementations relied on the system linker to load Zygisk modules and the Zygisk library itself. Both Zygisk Next and ReZygisk were the first to step up the game few months ago, and utilize custom linkers to load the Zygisk modules.

However, the libzygisk.so was still being loaded with the system linker. ReZygisk, a day ago, got a huge improvement: the utilization of a custom linker to load libzygisk.so remotely, removing the need of heuristics or any code to hide Zygisk traces from the linker.

This makes it impossible for ReZygisk to be detected through such vectors, which were the most abused by RASPs (Runtime application self-protection) to detect the existence of Zygote injectors.

3. Installation size reduced

ReZygisk and other forks of Zygisk Next, changed a lot of things. However, one behavior was kept: copy the library files to a temporary folder to change their permissions. This made the installation size be significantly bigger.

Now we removed that, not only leading to the simplification of the system architecture of ReZygisk, but also reducing the installation size by around 30%.



It takes time, but they come as they should be in the end. We expect to deliver more improvements over time, to soon release Release Candidate 5.

Also, an update for translators to update their respective language's README, as it has been updated.



Your dedication is for nothing, their criticism will not ever stop.
They never left their minds, but in the end you will get to the top.
It is subjective, but what matters are the eyes of those who cares,
And to the eyes-less, find the answer for all of their questionnaires.
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from KernelSU Next Bot
KernelSU_Next_v3.0.0-106-gab7b99e3-spoofed_32963-release.apk
9.3 MB
Dev Manager Build (Spoofed)
#ci_2963

kernel: fix bad pointer dereference for uname spoof

Commit
Workflow run
KernelSU_Next_v3.0.0-106-gab7b99e3_32963-release.apk
9.3 MB
Dev Manager Build (Normal)
#ci_2963

kernel: fix bad pointer dereference for uname spoof

Commit
Workflow run
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM