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

More embedding guide updates

Browse Source
This commit is contained in:
zzz
2023-01-03 07:47:37 -05:00
parent 878893a7c3
commit fc9abe46b1
1 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
i2p2www/pages/site/docs/applications/embedding.html
View File

@ -45,6 +45,7 @@ Some of the following only applies to the Java router.
Ensure you meet the license requirements of the software you are bundling. Ensure you meet the license requirements of the software you are bundling.
{%- endtrans %}</p> {%- endtrans %}</p>
<h2>Configuration</h2>
<h3>{% trans %}Verify default configuration{% endtrans %}</h3> <h3>{% trans %}Verify default configuration{% endtrans %}</h3>
<p>{% trans -%} <p>{% trans -%}
@ -152,6 +153,17 @@ for high-traffic servers and applications.
<h3>Specify SAM SIGNATURE_TYPE</h3>
<p>
SAM defaults to DSA_SHA1 for destinations, which is not what you want.
Ed25519 (type 7) is the correct selection.
Add SIGNATURE_TYPE=7 to the DEST GENERATE command,
or to the SESSION CREATE command for DESTINATION=TRANSIENT.
</p>
<h3>Limit SAM Sessions</h3> <h3>Limit SAM Sessions</h3>
<p> <p>
Most applications will only need one SAM session. Most applications will only need one SAM session.
@ -166,7 +178,7 @@ In almost no situation should you require a unique session per-connection.
Without careful design, this could quickly DDoS the network. Without careful design, this could quickly DDoS the network.
Carefully consider if your security goals require unique sessions. Carefully consider if your security goals require unique sessions.
Please consult with the Java I2P or i2pd developers before implementing per-connection sessions. Please consult with the Java I2P or i2pd developers before implementing per-connection sessions.
</p> </p>
@ -183,6 +195,7 @@ See i2psnark for code that reduces tunnel count and then closes the tunnel, even
{%- endtrans %}</p> {%- endtrans %}</p>
<h2>Life Cycle</h2>
<h3>{% trans %}Updatability{% endtrans %}</h3> <h3>{% trans %}Updatability{% endtrans %}</h3>
<p>{% trans -%} <p>{% trans -%}
@ -217,6 +230,8 @@ If your average uptime is less than an hour, I2P is probably the wrong solution.
{%- endtrans %}</p> {%- endtrans %}</p>
<h2>User Interface</h2>
<h3>{% trans %}Show Status{% endtrans %}</h3> <h3>{% trans %}Show Status{% endtrans %}</h3>
<p>{% trans -%} <p>{% trans -%}
@ -245,6 +260,8 @@ it may be helpful to provide an option or a separate package to use an external
{%- endtrans %}</p> {%- endtrans %}</p>
<h2>Other Topics</h2>
<h3>{% trans %}Use of other Common Services{% endtrans %}</h3> <h3>{% trans %}Use of other Common Services{% endtrans %}</h3>
<p>{% trans -%} <p>{% trans -%}
@ -375,6 +392,7 @@ Hang out in IRC #i2p-dev. Post on the forums. Spread the word.
We can help get you users, testers, translators, or even coders. We can help get you users, testers, translators, or even coders.
{%- endtrans %}</p> {%- endtrans %}</p>
<h2>Examples</h2>
<h3>{% trans %}Application Examples{% endtrans %}</h3> <h3>{% trans %}Application Examples{% endtrans %}</h3>