On Friday 22 October 2010 22:14:35 Robert Hailey wrote: > > On 2010/10/15 (Oct), at 1:00 PM, Robert Hailey wrote: > > On 2010/10/15 (Oct), at 9:29 AM, Volodya wrote: > >> There is an option in the configuration which turns on caching of > >> the 'local or nearby requests', you can turn it on to speed up such > >> requests. However, you should note that it will be significantly > >> easier to determine what you've been downloading/viewing while that > >> setting is turnt on. > >> > >> I hope this helps you. > >> > >> - Volodya > >> > > > > Yes, that is helpful. Thanks for pointing it out. > > > > -- > > Robert Hailey > > > > btw. I've activated this on my nodes and the difference is phenomenal. > Much happier "end user experience."
That is odd. It implies the client-cache isn't working or perhaps is just too small. Can you elaborate please? Stuff you have fetched recently should still be in your client-cache and should load quickly. > > Was this option disabled by default b/c of bloom-filter sharing? It's enabled at LOW network seclevel. It's partly because of bloom filter sharing but datastore probing via timing attacks is possible even without bloom filter sharing. Look up "I know what you downloaded from Freenet" aka The Register's attack. > > I really think the argument for sniffing your store/cache is only > relevant if the majority of nodes have this option disabled (otherwise > popular "sites" would be cached b/c they are popular, and unpopular > would cache b/c the requests trying to find them, no?). I'm not following. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20101023/732b55da/attachment.pgp>
