Skip to main content
8 events
when toggle format what by license comment
Jul 1, 2019 at 15:11 vote accept inf3rno
Jul 1, 2019 at 12:43 answer added John Deters timeline score: 3
Jul 1, 2019 at 6:56 comment added Lie Ryan Most modern salted symmetric encryption like AES wouldn't be vulnerable to known plaintext attack. As long as the salt is unique for each data and the plaintext and encrypted text doesn't have a uniquely identifiable data sizes. You can add some paddings to limit your data sizes to fixed sizes at the cost of larger encrypted data size.
Jul 1, 2019 at 6:34 comment added inf3rno @MikeScott I can change the algorithm and decrypt + encrypt the whole database again, but it takes a lot of effort, so I would do it maybe once in 5-10 years if it is really needed. I can save the key id along with the encrypted data so I can use multiple keys and change keys frequently to avoid overusage if I need to do that.
Jul 1, 2019 at 6:27 comment added inf3rno @MikeScott It is GDPR user data, so profile, email address, etc. Not sure how GDPR deals with decryption after 40 years, probably the application won't exist that long. :D
Jul 1, 2019 at 5:49 comment added Steffen Ullrich "I think the main danger here that the database can be stolen and not that somebody falsifies the data, so symmetric encryption is fine, we won't need different keys for read and write." - The difference between symmetric and asymmetric encryptio is not about falsifying data (integrity) but to allow a public key for encryption but to have a secret key for decryption. And asymmetric crypto is usually used combined with symmetric crypto - allowing different symmetric keys while keeping the public/private key the same. As for known plain text attacks: that's what random IV are for.
Jul 1, 2019 at 5:19 comment added Mike Scott How sensitive is the data? For how long will it be sensitive — is it a problem if it’s decrypted in forty years’ time?
Jul 1, 2019 at 5:13 history asked inf3rno CC BY-SA 4.0