-
Notifications
You must be signed in to change notification settings - Fork 68
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
Key dumping starting version 2.7 #8
Comments
Can u ping me pls, when you get a key for 2.7 (Hope it doesnt take a whole month xD) |
Currently working on it, the file |
@ToaHartor If you want, i can help you to make UI on Python for this app |
I still don't know about a GUI option to be honest, maybe in the future. |
@ToaHartor Hey check this: |
That's clean ! I will link your repository here |
Update on this : the PR #11 made it clear, the key is given in one of the packets, named |
Can anyone draw an icon for programm? |
Closing this issue, as the data has been verified |
How can packets be monitored? Software to use? I am interested in getting the latest version, 3.8 code on my own. |
From version 2.0 until version 2.6, the second key for the cutscenes of the current version was available in the dispatch's encrypted config, which was quite easy to retrieve.
However starting version 2.7, the second keys might now be sent when the game needs it, therefore either in a packet at the beginning of a cutscene during a quest or during the login. The version file (right below) also gives the several groups of cinematics that have the same second key. It would then require a rigorously taken packet capture to get the key associated with the cutscene viewed.
There's a strong probability that, like for the previous versions, they would give the keys in the Video Versions file (as the code would suggest). So, to get the keys from 2.7, we would have to wait for the 2.8 release.
Until 2.8 drops, I'll try to verify my theory....
The text was updated successfully, but these errors were encountered: