3 ms·
Great question. One of the things we're trying to do is encrypt everything in a way that requires multiple hacks to actually decrypt the content. We're keeping
by samiur1204 8y ago
Great question. One of the things we're trying to do is encrypt everything in a way that requires multiple hacks to actually decrypt the content. We're keeping the encrypted content on our databases, but using multiple private keys (one tied to the user, one stored in a separate vault). Journal employees cannot decrypt a user's data without unlocking a vault on our end, and our auth store.
- radicaldreamer 8y agoHow do you respond to subpoenas?
- regular_dev34 8y agoSecurity is always relative however in this case its a little bit more risk. It definitely gives some protection against the database being hacked. I wonder if you allow the user credentials for the sites to be read back by the user on screen? One of the core principals is to never store the password credentials in plain text, however the way the service works you have to store them in plain. Another concern is if the service can read and gather the secrets from both the data stores to make the request then its a matter of some writing an API to leak that information by mistake or intentionally.