Chrome / Firefox：扩展程序的访问源 [英] Chrome/Firefox: access source of an extension

问题描述

Chrome或Firefox是否使您的扩展程序的源代码对主机开放？如果是，那么Mac上的文件夹在哪里？

解决方案

是您的扩展程序是以解释和未混淆的语言编写的。对于任何Firefox扩展，如果你保存.xpi文件而不是安装，它只是一个zip文件，而你可以使用任何归档工具（例如7zip或WinZip）打开它。

.crx文件Chrome也是如此。作为测试，我只是下载并打开了 Google Mail Checker Plus 使用7zip，它看起来像这是完全用JavaScript编写的，所有的源代码都可以被读取。

在任何情况下，多少可用的源代码可以从这取决于扩展中使用的语言。

Google Chrome将扩展程序安装到 〜/ Library / Application Support / Google / Chrome / Default / Extensions /< EXTENSION_ID> / 并将其注册到其首选项文件（根据这个）

正如heb所说，Firefox安装扩展名为 〜/ Library / Application Support / Firefox / Profiles / PROFILE_ID / extensions / EXTENSION_ID /

Do Chrome or Firefox make your extension's source code open to the host machine? And if yes where are the respective folder on Mac?

解决方案

Yes, assuming some or all of your extension is written in an interpreted and un-obfuscated language. Plain Javascript is common for extensions in both browsers.

For any firefox extension, if you save the .xpi file instead of installing it, it is just a zip file and you can open it with any archive tool (e.g. 7zip or WinZip).

The same goes for the .crx files Chrome. As an test, I just downloaded and opened the .crx for Google Mail Checker Plus using 7zip, and it looks like this is entirely written in javascript and all the source can be read.

In either case, how much usable source code you can get from this depends on the language(s) that are used in the extension.

Google Chrome installs the extension into ~/Library/Application Support/Google/Chrome/Default/Extensions/<EXTENSION_ID>/ and registers it in its Preferences file (according to this).

As heb says, Firefox installs the extension to ~/Library/Application Support/Firefox/Profiles/PROFILE_ID/extensions/EXTENSION_ID/

这篇关于Chrome / Firefox：扩展程序的访问源的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！