The existing Flash encryption solution is studied. There are two kinds of
1. Write an HTTP server yourself, users can't download the Flash files on the HTTP server.
Disadvantages: Users can get this Flash file from the IE temporary file inside the machine, because the Flash player will first download this file to a local temporary folder. So you can't solve the Flash version protection problem
2. Encrypt the existing Flash file encryption tool
Disadvantages: Existing encryption tools, encrypted Flash files. Use the corresponding decryption tools to easily obtain the source file. The copyright is highly required for Flash content. Can't achieve the protection requirements
The root of the problem:
I feel that the problem is to expose to the user's SWF. It is a format that can be parsed. Since the SWF can be played by the Flash player correctly parsed, then this SWF can be cracked. So really protect the SWF document, you need to swF Direct file encryption operations. Then write a player for this encrypted SWF document to decrypt play.
The advantages of this:
1. You can customize some encryption schemes in the reproducing solution according to the user's needs, which is convenient for the user's existing product system.
2. Using the player, you can act as a platform to present the product to the user.
Welcome to contact me for this aspect. Discuss!
