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.

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

For guidance, for help #16

Closed
flyOfYW opened this issue Feb 26, 2019 · 4 comments
Closed

For guidance, for help #16

flyOfYW opened this issue Feb 26, 2019 · 4 comments

Comments

@flyOfYW
Copy link

flyOfYW commented Feb 26, 2019

I found a problem with WeChat-related appkey, hexByObfuscatingString methods, such as "wxaa45ad08facad578", "wxaa45ad08uhtad578", I don't know if there is a way to solve it @pjebs

@pjebs
Copy link
Owner

pjebs commented Feb 26, 2019

can you provide more details

@flyOfYW
Copy link
Author

flyOfYW commented Feb 26, 2019

Obfuscator *o = [Obfuscator newWithSalt:[YWVIewLisCtr class],[NSString class],nil];
NSString *origParseKey = @"wxf1e5d5ee0f9ef510";
[o hexByObfuscatingString:origParseKey];

2019-02-26 11:35:04.532 Example[5363:203129] Could not obfuscate: wxf1e5d5ee0f9ef510 - Use different salt
2019-02-26 11:35:04.532 Example[5363:203129]

decoded: JEG3i8R9LAXIDW0kXGHGjauak0G2mAjPacv1QfkO
ob:JEG3i8R9LAXIDW0kXGHGjauak0G2mAjPacv1QfkO

I found that rules like "wxaa45ad08uhtad578" have a high probability of error

@pjebs
Copy link
Owner

pjebs commented Feb 26, 2019

You need to add way more classes for security reasons. 2 is not enough.

@flyOfYW
Copy link
Author

flyOfYW commented Feb 26, 2019

Ok, thank you

@pjebs pjebs closed this as completed Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants