JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler

NEW : We have got a new blog where we post some interesting SWF internals info.

List of issuesList of issues

#402 Can't decompile Flash Antidecompiler 6.9 obfuscated code
Author: user focus
Date created:
Type: bug
Visibility: Everybody
Assigned to:
State: closed Help

Subj happens with attached file.
developer
Fixed in source control. Will be incuded in the next release.
Assigned:developer honfika
developer
Nightly build (ac7d416d6a03) released. Please try it.
State: new→upgraded
user
Thanks, not freezing now! Some methods can't be decompiled though (like generateCipher() in main class). This issue may be renamed to "Can't decompile Flash Antidecompiler 6.9 obfuscated code".
developer
Yes, but it is a common problem, i have a lot of sample swfs with this problem...
developer
State: upgraded→new
Title: Flash Antidecompiler 6.9: FFDec freezing while decompiling→Can't decompile Flash Antidecompiler 6.9 obfuscated code
admin
As I already said in other deobfuscation issues: There are many issues about obfuscated code. Deobfuscation technics used in FFDec are not the best ones. There is no perfect solution. It takes a lot time to investigate where the problem lies and unfortunately I am no longer in a mood for fixing this. If I change something about deobfuscation, other part stops working, over and over again... I am sorry, but I give this low priority :-(.
State: new→postponed
user
Maybe different deobfuscation options would help to solve this? To let users choose which deobfuscation tricks to use in every particular case?
developer
Assigned:
developer
Assigned:
admin
Assigned:
admin
Assigned:
admin
Assigned:
developer
Changed the label, because despite of the filename, this is not an AS2 file, this is AS3.
admin
I don't know anyone is still interested since flash is gone, but this seems to be a way better in nightly 1779. Actually, there are still some §§gotos in the code, since I think the generateCipher method is manually obfuscated and has these gotos inserted on purpose. I think we cannot handle them better than this.
State: postponed→upgraded
admin
State: upgraded→closed