![]() |
![]() |
![]() |
![]() |
![]() |
||||||||||
|
||||||||||||||
![]() |
|
#1
|
|||
|
|||
![]() DotFuckScator is a reversing engineering tool used to remove string encryption
from dotfuscator protected files If the original file was strong name signed DotFuckScator will create a new keypair and re-sign the file with this pair, be carefull since file depending on this file will need to be edited manualy to support the new strong name signature. You can use RE-Sign for this and the editor of your choice Also if you like the file re-signed with a specific key place your key in the same folder as the file you are about to process and rename it to DotFuckScator.snk now DotFuckScator will use this key for the re-sign process. ![]() Check the reteam.org tool page for the download link |
#2
|
|||
|
|||
![]() lool ! nice work again.
I especially like the name of this tool ![]() and I'm sure 'they' will love it aswell ![]() |
#3
|
|||
|
|||
![]() LibX can you update this to work with the latest dotfuscator? Or do you know how the newest encryption work?
Because with my own tool and this I get a ton of half decrypted strings. I have the encrypted string. \uf285\uf087\ufe89\ud98b\ufd8d\uf58f\ue091 which decodes to txtuser but my tool and yours decodes it as txt癳ser I think it has something to do with the flag at the end of the user string. Because if you change the flag from 1 to 0 it causes the program to decrypt to that too. |
#4
|
|||
|
|||
![]() I see the problem but iam not sure what ur trying to tell me in the last part, could u explain this please?
|
#5
|
|||
|
|||
![]() Ok check lastest release of DotFuckScator its fixed
Thx for the bugreport ![]() Regards LibX // RETeam |
#6
|
|||
|
|||
![]() Quote:
Edit: Hmm it gives me a "Object reference not set to an instance of an object" when I tried it. Last edited by high6 : 09-23-2008 at 05:10 PM. |