-
Replace fake app-hardening with real runtime protection, fold into encryption
frostbyte_neo 发布于
2026-06-01 11:08:25 +00:00 | 750 次提交 在此版本后已推送到 mainThe "App Hardening" toggle was a placebo: the build-time engine under
core/protection/ only wrote decorative .dat files and a hardening_meta.json
claiming 27 protection layers, while nothing at runtime ever read them and the
real classes.dex / .so were left untouched. Users correctly reported it did
nothing.What this does instead:
- Wire the already-present RuntimeProtection (anti-debug / anti-Frida /
DEX-CRC tamper checks) into the shell at launch via a new ShellHardeningGuard,
driven through the ApkConfig -> JSON -> ShellConfig pass-through chain. - Fold runtime protection into resource encryption: enabling encryption now
also enables the launch-time checks, with a configurable ThreatResponse
(LOG_ONLY default = zero impact on normal users, plus SILENT_EXIT /
CRASH_RANDOM). Only HIGH+ threats trigger a response, so root/emulator/Xposed
never block legitimate users. - Delete the fake core/protection/ engine (7 classes) and the standalone
AppHardeningConfig, HardeningConfigCard, the Play-policy hardening rule, and
all orphaned hardening strings. - Rewrite the README/README_CN security sections honestly: real AES-256-GCM
resource encryption (noting the no-password key is derived from public
package+signature) plus lightweight runtime protection that raises the bar
for dynamic analysis but cannot stop static reverse-engineering of the
open-source host.
下载附件
- Wire the already-present RuntimeProtection (anti-debug / anti-Frida /