Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
04-23-2011 07:30 PM
10-21-2011 09:39 AM
10-25-2011 06:30 PM
If you want a real obfuscator, secureSWF is the one. The DComSoft and Amayata products don't do much to the bytecode other than add some nonsense bytes to function headers that trip up decompilers. So they're generally about one version ahead of the decompilers.
secureSWF does actual obfuscation with variable/function renaming, control flow spaghettification, etc. It's more expensive than the other two, but it works.
I haven't tried to pull a .bar or .swf off a Playbook, but it's a pretty trivial process to pull a .apk off an Android and then extract the .swf. And I can confirm that not very many of 'em are obfuscated, as I could decompile 'em easily.
10-25-2011 06:32 PM
12-16-2011 07:03 AM
I tested the SWF produced from SWF Protector on 3 popular decompilers and had no luck reverse engineering the files. The protected SWF even crashed 1 of the decompilers. When I opened the SWF in the Flash Player, everything I set up still functioned properly. When testing SWF encryption tools in the past, I’ve found that the encryption breaks my SWF file.