There was a request for me to be more clear about "Bootstrapping with Keyindexes" The bootstrapping process is currently outside freenet. You use DNS and the web to get the IP of "octayne" running "inform.php". It is bootstrapping because the installation software is preset with the web address for the "octayne" system now. Since the capability now exists to have an in-freenet keyindex that is updated daily, why not have the bootstrapping process go to an "in-freenet" keyindex that is known to exist because some machine within the Freenet project is doing the daily insertions to it. This would be very similar to what octayne does now, except it would be in-freenet. This makes the freenet nodes listing exist under a private key so that web hacks could not somehow mangle or get large portions of the listing. Perhaps a "nodes.config" file could be included in the distribution so that newbies could find the site there. If you wanted heightened local node protection you could have the installation software remove the "nodes.config" file after it has verified connectivity with the in-freenet source(s) for node information. The "nodes.config" could be changed fairly easily to modify where and how the bootstrapping information would be found by newbie systems. If the newbie system fails to get bootstrapped from the "fn_bootstrap" keyindex it could fall back on "inform.php". However, having the newbie go in-freenet first means that the system grows into depending on itself first. My understanding of version 0.4 is that more security may be built-in by having the datastore a single unit and perhaps encrypting it. This means your bootstrapping could be more secure as well. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/devl
