Data Density Attack

[jlpell]

@neo

If you did do indirection on all chunks then what is to stop a slightly longer attack and scan through all the public files and look for a hit on your Vault. Then do the attack anyhow. So indirection DOES NOT solve the attack, it only makes it take a little longer before you can get results.

@dirvine

If you are talking about public data only then you could go to some lengths and try and work out if you have a chunk, not easy but possible, not for private data though. If it is public data then there is much less to worry about I would imagine. Its private data I am much more concerned about staying private. Public data by default would be identifiable at some stage, so should not be a surprise, the issue is do you know you are storing it, well no you don’t unless you go to lengths beyond what a normal user would do.

privacy of public data is a whole other subject

Dirvine is essentially talking about constant indirection from the vault manager to the vault then, is he not? Is our current discussion about the data density attack simply reinventing the wheel or have we identified another valuable layer of indirection to stop someone from being about to " go to lengths beyond what a normal user would do"?