Username
Password
I think the last thread concluded that it's impossible without the 256 bits key.end of the story.Lesson: blizzard owned us....... for the time being...
Hmm.. There must be something in the beta files that are encrypted which gets decrypted the same way.
The 256 bit key I believe is retrieved somehow by the Authentication code for sure than. The Authentication Code and the Decryption code are the one and the same. As proof I present that there is no storage space for authentication code, however when you change a jump address from jz to jnz it opens a screen where you manually enter the authentication code, this than goes directly down to a section of code containing hasValidDecryptionKey.This means that the authentication key is also checked. Then there are 3 characters that are restricted. So that narrows down the decryption key further.
Quote from: darkrei9n on July 19, 2010, 09:57:09 PMThe 256 bit key I believe is retrieved somehow by the Authentication code for sure than. The Authentication Code and the Decryption code are the one and the same. As proof I present that there is no storage space for authentication code, however when you change a jump address from jz to jnz it opens a screen where you manually enter the authentication code, this than goes directly down to a section of code containing hasValidDecryptionKey.This means that the authentication key is also checked. Then there are 3 characters that are restricted. So that narrows down the decryption key further.Yeah, it's the auth code. Now all you gotta do is guess a 10 - 20 digit & alphanumerical number.
...however when you change a jump address from jz to jnz it opens a screen where you manually enter the authentication code...
...1. They also find authentication key and decription key is the same and get to the screen for manaully entering the authentication code. So everything still boils down to getting the salsa20 decription key....