> Good lord! You have to go through all of THAT just to insert something into > the network?? What a kludge. Even if you somehow manage to hide this from > the users, you still have to do all of it programmatically, and there goes > any hope of a simple design.
It's actually quite simple, certainly more simple than what you proposed. And it's totally client-side and already coded, so it's certainly more easy to implement. Here's how you insert a key, from a user's perspective: java Freenet.client.KeyIndexClient -insert keyindex -key key For instance, KeyInsertClient -insert test-index -key freenet:KSK at test-key You can also do KeyIndexClient -list keyindex to get a list of keys from an index. > What is the suggested solution for the problem > of locating a keyserver? The mere existence of key servers compromises the > network by giving attackers central point(s) of failure. You still don't understand the mechanism. There is no key server. It's just a bunch of files in Freenet. The "keyindex" parameter is just a name you make up. For instance, "sites" is a good name for an index which contains keys pointing to freesites. And "steve" is a good name for an index which you submit things to if you want them to show up on Steve's Key Index. _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl >From - Fri Apr 20 11:47:17 2001 Return-Path: <devl-admin at freenetproject.org> Received: from hawk.freenetproject.org (postfix@[4.18.42.11]) by funky.danky.com (8.9.3/8.8.7) with ESMTP id TAA26705
