update reseed docs for su3

i2p2www/pages/site/docs/how/network-database.html

@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}{% trans %}The Network Database{% endtrans %}{% endblock %}
-{% block lastupdated %}{% trans %}October 2013{% endtrans %}{% endblock %}
-{% block accuratefor %}0.9.9{% endblock %}
+{% block lastupdated %}{% trans %}June 2014{% endtrans %}{% endblock %}
+{% block accuratefor %}0.9.14{% endblock %}
 {% block content %}
 <h2>{% trans %}Overview{% endtrans %}</h2>
 
@@ -744,6 +744,13 @@ Several defenses are possible, and most of these are planned:
 Disallow fallback from HTTPS to HTTP for reseeding.
 A MITM attacker could simply block HTTPS, then respond to the HTTP.
 {%- endtrans %}</li>
+  <li>{% trans %}Bundling reseed data in the installer{% endtrans %}</li>
+</ul>
+
+<p>{% trans -%}
+Defenses that are implemented:
+{%- endtrans %}</p>
+<ul>
   <li>{% trans -%}
 Changing the reseed task to fetch a subset of RouterInfos from
 each of several reseed sites rather than using only a single site
@@ -753,7 +760,12 @@ Creating an out-of-network reseed monitoring service that
 periodically polls reseed websites and verifies that the
 data are not stale or inconsistent with other views of the network
 {%- endtrans %}</li>
-  <li>{% trans %}Bundling reseed data in the installer{% endtrans %}</li>
+  <li>{% trans -%}
+As of release 0.9.14, reseed data is bundled into a signed zip file and
+the signature is verified when downloaded.
+{%- endtrans %}
+See <a href="{{ site_url('docs/spec/updates') }}#su3">the su3 specification</a> for details.
+</li>
 </ul>
 
 <h3>{% trans %}Query Capture{% endtrans %}</h3>