On Mon, Jul 7, 2008 at 5:48 PM, Cliff Wells <[EMAIL PROTECTED]> wrote: > > Sometimes this type of security is required (by law or PHB's), but most > people who ask this sort of question are simply following a cargo-cult > mentality of believing that source code must be kept secret, without > much thought as to why and what the risks/benefits really are. If your > code is so unique as to be worth protecting this way then it's probably > worth patenting whatever amazing algorithm it contains. If it's not > worth the few thousand dollars you'll spend applying for a patent, then > it's probably not worth the few thousand dollars of development time > you'll spend trying (almost certainly unsuccessfully) to protect your > code by technological means. > I think this is the most important statement around. After all it's all binary which can be turned into opcodes which can be turned into ASM which can be turned into C,etc. There is no way you can't hide something that is supposed to run on the client machine from the client. So if you want to do it for being cool, go ahead if not use the correct way.
Someone ones said, any security scheme can be broken with enough time in your hands. > Cliff > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
