note 106582 deleted from intro.bcompiler by thiago

Note Submitter: Charles Hannon, PhD ---- I fully support this effort and while it is true that any released binary file can be exploited, the last comment completely misses the point. By using something like bytecode, you are making it harder for someone to see your code, and thus, are making a good faith effort to protect your IP. In a perfect world, people would not try to steal your IP or your physical property. Since people will steal your stuff, following the same logic above, the author would have us EITHER leave our keys in our car, keep our house doors unlocked, and walk down dark alleys at night OR living in a cave that we never leave. I have many years of security experience. The common rule of thumb in encryption is to encode something past the point that normally makes it worth decrypting. NSA can break into your SSL traffic any time they want, but why bother. There is normally nothing there worth anything (to them) and they have other uses for their CPU cycles. The thing that protect the data in your SSL transaction is not the rather low-level method of encryption being used, but the sheer volume of SSL traffic that makes it doubtful anyone will even bother to decrypt it. Some companies, like mine, need to pay their employees so we need to do the best job we can at not releasing the results of our NRE. I plan to use something like bytecode to protect our new product to reduce (not eliminate) the chance the code will be used illegally. People who are smart enough to reverse engineer bytecode, should be smart enough to read a licensing agreement and understand that a company has legal recourse for breaking it.