decentralized-identity / confidential-storage

Confidential Storage Specification and Implementation
https://identity.foundation/confidential-storage/
Apache License 2.0
80 stars 23 forks source link

Should metadata be plaintext in Encrypted Data Vaullts? #79

Closed OR13 closed 4 years ago

OR13 commented 4 years ago

I suggest no:

https://www.theverge.com/2013/7/17/4517480/nsa-spying-prism-surveillance-cheat-sheet

In an impassioned plea made by Microsoft on July 16th, the company’s general counsel Brad Smith said: "We believe the US constitution guarantees our freedom to share more information with the public, yet the government is stopping us."

Imagine if it didn't matter what they were forced to share by a NSL... because they couldn't see anything.

dhh1128 commented 4 years ago

Hyperledger Indy wallets (not mobile apps, but the storage containers underneath them) encrypt nearly all metadata by default; it is possible to erode this position slightly, but not in toto. See https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0050-wallets#types-of-sovereign-data and also the "Tags and Queries" section just above that.

The reason we did this is that these containers are specialized to store data on the more sensitive side of the sensitivity spectrum. They're not for storing your cat photos.

Because EDVs aspire to store all data, the problem space is broader, and that creates more tensions. Having metadata be plaintext increase the options and decreases the complexity (and probably size and performance) of your indexing strategy, but it also lets configuration shoot the user in the foot when it's done unwisely. If it were me, I'd probably pick secure by default and side with Orie that the answer should be "no."

OR13 commented 4 years ago

Closing we have reached consensus on this issue.