We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
hook得到的aes key来自-[AuthSectResp init]中的置入的SetCliDbencryptKey,提取对应目录下的聊天记录msg_*.db可以使用此key解开得到聊天记录。
-[AuthSectResp init]
SetCliDbencryptKey
msg_*.db
The text was updated successfully, but these errors were encountered:
看了一下确实是数据库的key, 数据库用了32个字节的key, 小程序这边使用的是前16个字节
Sorry, something went wrong.
从图上看,感觉是从通过请求获取的key, 如果是这样的话,这个key 算法就无法逆向了...
dbEncryptKey确实是来源于server 目前猜测是server通过设备的一些指纹以及uid计算得到固定的dbEncryptKey 唯一值得欣慰的是在同一设备上反复登录,dbEncryptKey不会改变...不必反复hook获取key🤣
No branches or pull requests
hook得到的aes key来自
-[AuthSectResp init]
中的置入的SetCliDbencryptKey
,提取对应目录下的聊天记录msg_*.db
可以使用此key解开得到聊天记录。The text was updated successfully, but these errors were encountered: