On Sun, 2003-10-12 at 13:01, Reskill wrote: > I believe that without a clear definition between testing and stable > networks, recent occurrences regarding network degradation are bound > to happen again, sooner rather than later. Much better, then, to push > to a stable "clean slate" with the next well-tested stable build, and > always maintain this migration step with each significant new stable > release. > > It is definitely time that new procedures were put into place to safeguard > network performance and the freenet userbase, especially if any truly > worthwhile content is to surface in our network. >
I agree that better procedures are necessary. However, you should note that right now, all anyone who wants to knock freenet down needs to do is get about 50 nodes well integrated and then switch them to 6025 or so, using a version that claims to be something else. Having our developers and beta testers refrain from connecting to the live network is not going to remove the vulnerability which has just been exposed. Rather, we have to fix fred so that it blacklists nodes which are behaving badly. We will, I'm sure, refrain from testing this fix on the live network, since right now, the test would knock down all nodes not running the fixed version. Also, I'm working on a version of Version.java which supports more flexible ways of excluding nodes which are polite enough to specify their true build number but which are not working. -- Ed Huff
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
