I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

add info on plugin key whitelist

Browse Source
This commit is contained in:
zzz
2014-08-04 15:52:50 +00:00
parent d593b185e6
commit 75dbad02d3
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
i2p2www/pages/site/docs/spec/plugin.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2P Plugin Specification{% endblock %}
{% block lastupdated %}January 2014{% endblock %}
{% block accuratefor %}0.9.9{% endblock %}
{% block lastupdated %}August 2014{% endblock %}
{% block accuratefor %}0.9.14.1{% endblock %}
{% block content %}
<h3>Overview</h3>
<p>
@@ -243,7 +243,8 @@ This lists what happens when a plugin is installed by I2P.
<li>The .xpi2p file is downloaded.</li>
<li>The .sud signature is verified against stored keys.
If there is no matching key, the .sud is extracted, the key is loaded from the properties, then verified and stored.</li>
As of release 0.9.14.1,
if there is no matching key, the installation fails, unless an advanced router property is set to allow all keys.</li>
<li>Verify the integrity of the zip file.</li>
<li>Extract the plugin.config file.</li>
<li>Verify the I2P version, to make sure the plugin will work.</li>