|
From: Tod D. I. <to...@je...> - 2001-05-13 02:53:01
|
I still like the idea of only adverting that you know about a block, or rather, that you know a route to a block. The node requesting never needs to know where the block is coming from, it can choose whichever node responds 1st to get successive blocks from. Tod. On Sat, May 12, 2001 at 02:15:10PM -0400, Luke Hankins wrote: > > * If you disconnect and reconnect to a Blocks server it > > will only send you adverts for files that are available > > remotely, not for files it has within its own disk cache. > > This is to prevent scanners traversing the Blocks > > network and examining the files stored in each node. > > This means that the only way snoopers can associate a > > file with a particular Blocks server IP is to be directly > > connected to that server at the point the file was > > uploaded or cached. > > I _think_ that this problem can be solved by simply never advertising > to your neighbors that you have a block. Instead, make up a few > "loopback links" that point back to yourself and then use them to > pad out messages to at least 3 hops. > > This would prevent people who were directly connected to you from > finding out what you've got in your cache. (I think. I haven't had time > to check it out, but I think there would be a way for someone to connect > to you with three different clients and compare what routes you were > advertising to get more info.) > > It's a simple concept, but hard to explain without pictures. Should > I draw some? > > -Luke > > _______________________________________________ > Blocks-development mailing list > Blo...@li... > http://lists.sourceforge.net/lists/listinfo/blocks-development -- * All opinions expressed herein belong to Me. Tod D. Ihde. So there. * * HTTP://toon.jesus-crispie.com/ HTTP://www.jesus-crispie.com/ * * The average, healthy, well-adjusted adult gets up at * * seven-thirty in the morning feeling just terrible. * * -- Jean Kerr * |