> The one and only fundamental limitation of the current interface > offered by venti is that I can give it a score to something that > doesn't belong to me and it gives me the information back. It is > the limitation of the API, not the way data is managed.
I'm not sure how you'd fix this. What if only a portion of the block belongs to me and the other happens to be the password file? You need to draw boundaries at different security entities and that makes compression and especially duplicate suppression much less effective. You could argue that the security information provides its own boundaries, but making venti aware of them does add a lot of complications that in my opinion should be (and already are) solved elsewhere. I did propose that compression and encryption ought to be concurrent in venti, but that solves only part of the problem and raises new problems such as key management. ++L PS: As for the problem we're trying to solve, I'm afraid I've long ago lost track :-)
