3 ms·
That is a very interesting approach, however I can imagine that it can be quite a large database of encryption keys. I'll have to build a small system for this
by guywhocodes 7y ago
That is a very interesting approach, however I can imagine that it can be quite a large database of encryption keys.
I'll have to build a small system for this and try it.
- imglorp 7y agoOh, why? Holding one key for every human on earth would fit in 8 TB plus read-mostly replicas. You'd delete their key if they made GDPR removal request and the keyless, encrypted, immutable entries would be entombed in place.
- pookeh 7y agoWhat do you do when the data involves multiple people?
- shrimpx 7y agoIt's unclear (regardless of crypto shredding) what the delete policy should be if the data involves multiple people.
- randolorian 7y agoWhy would it? Typically you would have one stream per user.
- tunesmith 7y agoEvent: "User A sent Message X to User B". (I think the answer here is again to have PII be in other repositories, and only refer to them by id in the log.)
- specialist 7y agoGood question. Create alias proxies?