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

update

Browse Source
This commit is contained in:
zzz
2012-06-02 13:53:04 +00:00
parent aa1d4f4564
commit 752e1c6a42
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
www.i2p2/pages/how_networkdatabase.html
View File

@ -3,7 +3,7 @@
{% block content %} {% block content %}
<p> <p>
Updated August 2011, current as of router version 0.8.9 Updated June 2012, current as of router version 0.9
</p> </p>
<h2>Overview</h2> <h2>Overview</h2>
@ -78,7 +78,6 @@
Current statistics are limited to: Current statistics are limited to:
</p> </p>
<ul> <ul>
<li>1 hour average bandwidth (average of outbound and inbound bandwidth)
<li>Client and exploratory tunnel build success, reject, and timeout rates <li>Client and exploratory tunnel build success, reject, and timeout rates
<li>1 hour average number of participating tunnels <li>1 hour average number of participating tunnels
</ul> </ul>
@ -659,7 +658,8 @@ This attack becomes more difficult as the network size grows.
Several defenses are possible, and most of these are planned: Several defenses are possible, and most of these are planned:
</p> </p>
<ul> <ul>
<li>Switching from HTTP to HTTPS for reseeding, with SSL certificate verification <li>Disallow fallback from HTTPS to HTTP for reseeding.
A MITM attacker could simply block HTTPS, then respond to the HTTP.
<li>Changing the reseed task to fetch a subset of RouterInfos from <li>Changing the reseed task to fetch a subset of RouterInfos from
each of several reseed sites rather than using only a single site each of several reseed sites rather than using only a single site
<li>Creating an out-of-network reseed monitoring service that <li>Creating an out-of-network reseed monitoring service that