: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
Hello i have a question you can do to decompile protected swf files ? Thanks.
It depends on how the file is protected.
When it for example reads another SWF file with real code from encrypted byte stream I can
not do much about it - It needs to execute the code. (Loaders)
When the SWF file is protected by obfuscation - like control flow randomisation, FFDec
will probably decompile it. I do my best to decompile all sort of obfuscated code.
When identifier renaming protection is used, FFDec can rename invalid identifiers to
If you have some SWF files FFDec cannot handle, feel free to create an issue, I will try
to fix it.