Jack, >Any recommendations for a (preferably free/opensource) js obfuscator >that you've used and liked? I'm looking for something to take what >packer does to the next step: at minimum, obscure methods names, but >preferably scramble the dickens out of the file to reduce the likelihood >of reverse-engineering.
I would never bother trying to obfuscate. Whatever you do is still going to need to be able to be interpreted by the browser--which means it's still pretty easy to reverse engineer. Someone who wants the code's going to get it. What it will do is make troubleshooting legitimate issues a real PITA. That's just my $.02. -Dan
