OLD | NEW |
1 <div id="pageData-name" class="pageData">NPAPI Plugins</div> | 1 <h1>NPAPI Plugins</h1> |
2 | 2 |
3 <p> | 3 <p> |
4 Leveraging HTML and JavaScript | 4 Leveraging HTML and JavaScript |
5 makes developing new extensions really easy, | 5 makes developing new extensions really easy, |
6 but what if you have existing legacy or proprietary code | 6 but what if you have existing legacy or proprietary code |
7 that you want to reuse in your extension? | 7 that you want to reuse in your extension? |
8 You can bundle an NPAPI plugin with your extension, | 8 You can bundle an NPAPI plugin with your extension, |
9 allowing you to call into native binary code from JavaScript. | 9 allowing you to call into native binary code from JavaScript. |
10 </p> | 10 </p> |
11 | 11 |
(...skipping 75 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
87 a vulnerability, an attacker might be able to exploit that vulnerability | 87 a vulnerability, an attacker might be able to exploit that vulnerability |
88 to install malicious software on the user's machine. Instead, avoid | 88 to install malicious software on the user's machine. Instead, avoid |
89 including an NPAPI plugin whenever possible. | 89 including an NPAPI plugin whenever possible. |
90 </p> | 90 </p> |
91 | 91 |
92 <p> | 92 <p> |
93 Marking your NPAPI plugin "public" increase the attack surface of your | 93 Marking your NPAPI plugin "public" increase the attack surface of your |
94 extension because the plugin is exposed directly to web content, making | 94 extension because the plugin is exposed directly to web content, making |
95 it easier for a malicious web site to manipulate your plugin. Instead, | 95 it easier for a malicious web site to manipulate your plugin. Instead, |
96 avoid making your NPAPI plugin public whenever possible. | 96 avoid making your NPAPI plugin public whenever possible. |
97 </p> | 97 </p> |
98 | |
OLD | NEW |