On Sun, Aug 23, 2009 at 2:13 PM, sebastian.zim<[email protected]> wrote: > Why, couldn't we just find a code that could be easily transformed > into the machine code of whatever platform that version of chrome is > running on. It is vital that we find a way to hide the source of > extensions (I have already given you an example) from malicious users.
Obfuscation of source is a non-goal of the extension system. It was important for the web that people be able to "view source", it was important for Firefox extensions, and it will be important for Chromium extensions (the current issue with zip software frequently not recognizing crx files as zip files bothers me for this reason). If you really do want this, you have the option to include NPAPI plugins in your extension written in native code. Those are a lot harder to reverse engineer. But the JavaScript, HTML, and CSS in Chromium extensions will never be obfuscated. Any compilation will just be an optimization, and transparent to the developer. - a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
