4 ms·

How is this done? Google claims files are encrypted at rest and encrypted during transfer. Metadata inspection? Checksum during upload?

• dontcare007 5y ago
  Google dropped "don't be evil", so....
  • jvolkman 5y ago
    Did they?
    • twiddling 5y ago
      https://gizmodo.com/google-removes-nearly-all-mentions-of-dont-be-evil-from-1826153393 https://gizmodo.com/google-removes-nearly-all-mentions-of-do...
      • jvolkman 5y ago
        So it's still there.
• deathanatos 5y ago
  They just read the file. You seem to be under the impression that either of those imply end-to-end encryption, which they don't. (And in Drive's case, AFAIK, E2EE is not an offered nor advertised feature.) The data was encrypted during transmission to Google's servers, sure, but it was encrypted to them; similarly, yeah, they store it encrypted … and they have the key. (This isn't atypical either, sadly. E2EE is the exception…)
• x86_64Ubuntu 5y ago
  Encrypted at rest and transfer just means that if an unauthorized someone gets ahold of their backend systems, they can't read the file. It doesn't mean that Google can't maintain the key and use it to process and inspect the files. If they didn't have and use the key, they would never be able to create previews for files they keep, nor would they be able to offer a search function.