Encryption in plain txt files in mpq?
Posted: May 7th, 2009, 10:19 am
Originally I asked about this on hiveworkshop,but they don't endorse deprotection/extraction of others' map's contents,so I will repost here instead.
As a former/semi-active mapper I am particularly interested the inner works of modern Warcraft 3 custom maps,I usually open up protected/optimized maps with mpq editor of my choice,then read the .j file to understand how things are done/implemented in that map.
This simple and stupid method worked fine until I opened a map with an encrypted .j file,after a closer look at that mpq/w3x,it seems all plain text files(.j,.txt etc) are also encrypted,none of them makes sense as ascii/utf8,though the binary ones(.w3i etc) seem to be unmodified.
I opened a few encrypted files with hex editor,it turned out that all files have the same first few bytes " ff d6 fe cf 00 00 00 00 ",as you can see the first pair is well above 0x80(ascii range),so they are not a magic file extension header of any binary compression format that I know of.
I googled a bit and it seems few other maps also uses this kind of protection,but I couldn't find any info on decrypting the encryption or the encryption algorithm used on them.
So I am asking if anyone else has seen this kind of protection and knows how to decrypt the encrypted plain text files.
Thanks.
As a former/semi-active mapper I am particularly interested the inner works of modern Warcraft 3 custom maps,I usually open up protected/optimized maps with mpq editor of my choice,then read the .j file to understand how things are done/implemented in that map.
This simple and stupid method worked fine until I opened a map with an encrypted .j file,after a closer look at that mpq/w3x,it seems all plain text files(.j,.txt etc) are also encrypted,none of them makes sense as ascii/utf8,though the binary ones(.w3i etc) seem to be unmodified.
I opened a few encrypted files with hex editor,it turned out that all files have the same first few bytes " ff d6 fe cf 00 00 00 00 ",as you can see the first pair is well above 0x80(ascii range),so they are not a magic file extension header of any binary compression format that I know of.
I googled a bit and it seems few other maps also uses this kind of protection,but I couldn't find any info on decrypting the encryption or the encryption algorithm used on them.
So I am asking if anyone else has seen this kind of protection and knows how to decrypt the encrypted plain text files.
Thanks.