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

Get rid of brute forcing file seed #21

Open
Donkie opened this issue Dec 14, 2021 · 3 comments
Open

Get rid of brute forcing file seed #21

Donkie opened this issue Dec 14, 2021 · 3 comments

Comments

@Donkie
Copy link
Owner

Donkie commented Dec 14, 2021

Currently the file seed is attempted to be brute forced if the decrypt fails. I can't imagine this is how it's actually done in the engine. Figure out how to do this properly.

Bruteforcing added here: c68a32f

@thraidh
Copy link
Contributor

thraidh commented Aug 3, 2022

According to a shapes unlocker script found on the internet, it seems that the key number is N-13, if N does not work.
Using the FileHeader.cs conventions the unlocker script does:
If b1==5 and b2==32: seed=b3-13
else if (b1==0 or b1==1) and b3==128: seed=b2-13
The script would set b2=0 for the first case and b3=0 for the second and write back those and the seed, so I guess those are the flags indicating the locked shapes.
Since I don't have any DLCs I cannot verify any of this.

@Donkie
Copy link
Owner Author

Donkie commented Aug 4, 2022

Thank you, I will look into that

@kbrandwijk
Copy link

If I'm not mistaken, that's FS19 and FS17 DLC logic, respectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants