Hi. I have been testing the new announcement code, with 2 and 3 announcementThreads, on the public network. I end up with graphs with a big spike (in requests, and later in routing table), at one of the announcements. The other two are smaller, much smaller usually. Now, we know that announcing to a bad node can destroy your anonymity, so that your anonymity mainly relies on having good seeds. Would it be possible to track roughly which announcement is originally responsible for each reference? If an evil network that you announced to controls 90% of your noderefs, he can still probably compromize most of your traffic. This would give us a measure of the degree of potential vulnerability to this, and we could perhaps do something about it - for example reannouncing to some more nodes. At the very least it would give us some empirical data on the question "What is the appropriate value of announcementThreads?". Comments? Flames? -- Matthew Toseland mtoseland at blueyonder.co.uk amphibian at sourceforge.net Freenet/Coldstore open source hacker. Looking for $coding (I'm cheap) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020909/d38cd450/attachment.pgp>
