Rule 1:
Anyone with intelligence and determination will always obtain your code/keys/source/files/data
Anything you do simply increases the potential time/effort required to compromise
With or without SecureSWF, will people go to the trouble?
A quick Google suggest that not many attempts have been made to decompile SWF files created with secureSWF ... but they must still meet the specification of compiled bytecode ... so it just amounts to obfuscation. The lack of testing suggests:
- No one really has independently tested it, and therefore no value in its security can be made
- People have tested it, it is very effective and people didn't post the results
I think the former is more likely. If you said what the Flash app does, then these points might be more specific.
I would look for sources of data relating to how long after release these things have been reversed rather than the security of the system itself (which is irrelevant).
Also ensure that making your source secure-ish (rather than cooperating with the community) is the best strategy considering that at some point, a determined mind will be able to access your logic.
From a business point of view, your strategic position should not be in keeping your logic scrambled ... as this is futile. You can be as proprietary as you want ... but people will get around it (just ask the games industry). And heavy-handed security causes backlash (see DRM).
If you are convinced your application is so amazing that people will go to the effort of reversing it, look for another value proposition.
Flash is one of those things, like JavaScript, where there is only so much you can do and does it really matter? What good is the apps logic without the other links in the chain?
Anyway, look for the required effort to reverse the encoding rather than the perceived strength of the software's clients.
Anyway, Good Luck!
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…