Author: toad Date: 2008-03-19 13:30:40 +0000 (Wed, 19 Mar 2008) New Revision: 18596
Modified: trunk/website/pages/en/faq.php Log: Slight update to cancer nodes section Modified: trunk/website/pages/en/faq.php =================================================================== --- trunk/website/pages/en/faq.php 2008-03-19 13:28:11 UTC (rev 18595) +++ trunk/website/pages/en/faq.php 2008-03-19 13:30:40 UTC (rev 18596) @@ -484,12 +484,10 @@ identify even the most carefully designed malicious node and not keep sending requests to it. This issue is not fully dealt with by the current test code, but you can rest assured that a number of possible -solutions (for example allowing clients to vote on the validity of the -information returned on requests, and enforcing that all information be -indexed by a hash of the contents at the lowest level) have been on the -table and discussed for some time now.</p> +solutions have been on the table and discussed for some time now. +Several have been implemented (enforcing hashes or signatures on content, +per node failure tables, backing off from a node that causes timeouts ...)</p> - <p><b id="attackY">What about attack Y?</b><br> Freenet is still in testing and there are bound to be attacks found that we have
