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

copy requirements from old to policy

Browse Source
This commit is contained in:
idk
2023-01-05 02:34:17 +00:00
parent e236e86838
commit bfd5a73faa
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
i2p2www/pages/site/get-involved/guides/reseed-policy.html
View File

@ -5,6 +5,27 @@
<h2>{% trans %}Reseed Policy Information{% endtrans %}</h2>
<h3>2. Requirements</h3>
<p>
Requirements for running a public reseed server:
</p>
<ul>
<li>Well integrated running I2P router @ 24/7</li>
<li>Server with static IPv4 (2 cpu/ 2GB ram is fine)</li>
<li>Unix to run the golang solution</li>
<li>Own domain, sub-domain or an anonymous third-level domain</li>
<li>A self-signed SSL certificate, or an SSL certificate from <a href="https://letsencrypt.org" target="_blank">Let's Encrypt</a></li>
<li>Enough bandwidth and traffic volume - Around 15 GB/month as of December 2016</li>
<li>Up-to-date web server (Apache/nginx), HTTPS ONLY with TLS 1.2 and good ciphers</li>
</ul>
Optional:
<ul>
<li>fail2ban to protect you from botnets</li>
<li>GnuPG/PGP for signed/encrypted emails</li>
<li>IPv6</li>
</ul>
<p>{% trans -%}
When your setup is complete and ready for testing, we will need the HTTPS URL,
the SSL public key certificate (only if selfsigned), and the su3 public key certificate.