3 ms·
Ops, I thought I'm responding here. The server actually knows which pieces of B-Trees you access. But no more than that.
by michwill 12y ago
Ops, I thought I'm responding here.
The server actually knows which pieces of B-Trees you access. But no more than that.
- kevinnk 12y agoIf it knows what pieces you access, how do you prevent the sever from learning ordering?
- oh_sigh 12y agoIt knows the ordering of the encrypted data, but it doesn't know what the data is.
- JoshTriplett 12y agoThat seems like it reveals exactly the same kinds of information that range queries reveal.
- kevinnk 12y agoHow is that different than cryptDb then? CryptDb only reveals ordering as well (and only if the client requests it.)
- michwill 12y agoWell, actually the server doesn't know the ordering and how pieces of B-Tree refer to each other, it doesn't even know which data form the index and which are the actual data. Though, observing access patterns, it could probably deduce which data belong to the tree and some info about ordering (which will hold true until we re-balance the tree, which happens on inserts). I think, if we change objects each time we do queries, we can prevent this data leak.