Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by rdtsc on Tuesday October 31, 2017 @01:50PM
(#15595069)
Well the whole hard drive is not overwritten every time a file changes when using disk encryption, so definitely not necessary.
Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by mikeash on Tuesday October 31, 2017 @01:21PM
(#15594858)
Any encrypted disk image will work this way. It doesn’t require anything like homomorphic encryption, just a bit of metadata and key management.
Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by RasputinsBro on Tuesday October 31, 2017 @01:23PM
(#15594869)
No. AES encrypts blocks (I think 256kb?). So that's the only thing you have to sync.
Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by syrrim on Tuesday October 31, 2017 @01:53PM
(#15595102)
If you use plain AES ECB, then little penguins will show up in your encrypted data. You would want to use a disk encryption scheme, like XTS, where the encryption is not just based on the data of the block, but also on the index of the block, to prevent identical blocks at different locations from looking identical. You also want it to be based on a nonce of some sort, to prevent attackers from reverting a block to an older copy.
Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by RasputinsBro on Tuesday October 31, 2017 @02:17PM
(#15595290)
Penguins? What are you talking about?
I don't care about low-level encryption details. That's why I use encryption software instead of coding my own.
Re:Google Docs Is Randomly Flagging Files for Violating Its ...
by kevin_thibedeau on Tuesday October 31, 2017 @02:24PM
(#15595357)
It seems this will only be feasible when we have homorphic encryption ready.
If someone is interested on that kind of encryption, see "A FULLY HOMOMORPHIC ENCRYPTION SCHEME"[1] and "Fully Homomorphic Encryption without Bootstrapping "[2]
[1] https://crypto.stanford.edu/craig/craig-thesis.pdf
[2] https://eprint.iacr.org/2011/277.pdf