On Fri, Jan 11, 2013 at 1:32 AM, Diogo Resende <[email protected]>wrote:
> But what password are you talking about? Some kind of unique id / serial > that ensures the code runs? Can't that be a generated number? What about > people just wanting to close the source, but still distributed it freely? > If you want obfuscation (which is all compilation buys you), use an aggressive minifier like Closure. If you want protected credentials, use a system that allows you to only have them stored in memory. If you want secure authentication in distributed services, use a revokable, token-based system like OAuth. Running trusted code in an untrusted environment is not a problem that's solvable by hiding secrets in plain sight. It's pretty simple: Node is based on V8, which is a JIT compiler that uses statistical methods to generate optimized native code based on that code's execution profile. Its architecture precludes compiling to a static intermediate representation (as does the design of the language itself -- Function.prototype.toString requires access to enough of a high-level representation to reconstruct the code). If obfuscation is valuable, use a JVM-based environment like vertx or build Node.dart or something. This is a fundamental aspect of Node's implementation and isn't going to change. F -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
