forked from I2P_Developers/i2p.www
add info on plugin key whitelist
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
{% extends "global/layout.html" %}
|
{% extends "global/layout.html" %}
|
||||||
{% block title %}I2P Plugin Specification{% endblock %}
|
{% block title %}I2P Plugin Specification{% endblock %}
|
||||||
{% block lastupdated %}January 2014{% endblock %}
|
{% block lastupdated %}August 2014{% endblock %}
|
||||||
{% block accuratefor %}0.9.9{% endblock %}
|
{% block accuratefor %}0.9.14.1{% endblock %}
|
||||||
{% block content %}
|
{% block content %}
|
||||||
<h3>Overview</h3>
|
<h3>Overview</h3>
|
||||||
<p>
|
<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 .xpi2p file is downloaded.</li>
|
||||||
<li>The .sud signature is verified against stored keys.
|
<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>Verify the integrity of the zip file.</li>
|
||||||
<li>Extract the plugin.config file.</li>
|
<li>Extract the plugin.config file.</li>
|
||||||
<li>Verify the I2P version, to make sure the plugin will work.</li>
|
<li>Verify the I2P version, to make sure the plugin will work.</li>
|
||||||
|
Reference in New Issue
Block a user