Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[置顶] 防止被自动解密的方案讨论 #88

Open
MegatronKing opened this issue Nov 4, 2022 · 5 comments
Open

[置顶] 防止被自动解密的方案讨论 #88

MegatronKing opened this issue Nov 4, 2022 · 5 comments

Comments

@MegatronKing
Copy link
Owner

MegatronKing commented Nov 4, 2022 •
edited

解密的讨论收纳到这里，请不要新开issue。
@MegatronKing MegatronKing pinned this issue Nov 4, 2022
This was referenced Nov 4, 2022
Closed
Closed
@fh2002
Copy link

fh2002 commented Jan 10, 2023 •
edited

第一种解密函数在so中处理，缺点也很明显，逆向一下so就出来了。
第二种把解密函数放在热加载的dex中，通过动态加载来解密，apk中不含有解密的代码。
实现方法为：修改StringFog，当StringFog遍历到implement时，获取到implement的字节码，保存成单独的一个class,再转换成dex。再移除原implement中各函数的实现，只保留函数名。然后再把dex上传到服务器或加密到apk中，需要用到的时候再热加载，热加载后就能使用新的implement而不使用原implement。

@HolenZhou
Copy link

放在so中也不行，不用逆行MT也能一键解了。。。

@qx0657
Copy link

qx0657 commented Apr 19, 2023

THERE IS NO ABSOLUTE SAFETY

@swearl
Copy link

swearl commented Sep 13, 2023

不想麻烦, 我最后选择了
ysrc/AndroidObfuseDictionary + StringFog + Dex2C + 腾讯壳

@Genliese
Copy link

Genliese commented Sep 21, 2023 •
edited

不想麻烦, 我最后选择了 ysrc/AndroidObfuseDictionary + StringFog + Dex2C + 腾讯壳

6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@swearl @HolenZhou @MegatronKing @fh2002 @Genliese @qx0657