On Sun, Nov 02, 2003 at 10:54:29PM -0600, Tom Kaitchuck wrote: > One thing that recently occurred to me, that I had not previously seen > discussed here is that if someone were to analyze the contents of a data > store to try to determine if the owner of the store had requested a > particular file, one thing that might be particularly incriminating is the OS > storing the last accessed and last modified time stamps on the files. > > On the one hand it is easy to say that your node storing splitfile components > probabilisticly is not a problem, as they fall within your specialization and > so could easily have ended up there anyway. However the odds of them ending > up there all at around the same time is harder to refute. > > Also if the multi layer store, as discussed previously, was implemented the > same thing would apply. If the second data store were a single file, it > should write any of the 'last accessed' times to the disk. I know the 'I was > framed' defense would still work for the datastore, but we should make sure > that when nodes connect using premix routing that they stick with the same > node for a while, rather than just one per request or one per > splitfile/manifest request. This way large amounts of related data could be > placed there in a confined period of time as a result of normal network > operation, not just by someone out to get you.
Eh? The client cache would be temporary, and made useless when the computer is switched off. Combined with premix routing, you won't have any of the splitfile in the main store. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
