Secure cloud-based storage of data shared across file system objects and clients
Techniques to provide secure cloud-based storage of data shared across file system objects and clients are disclosed. In various embodiments, a primary encryption key is determined for an object associated with a plurality of component chunks of file system data. The primary encryption key is used to generate for each of said component chunks a corresponding chunk key, based at least in part on the primary encryption key and data comprising or otherwise associated with the chunk. The respective chunk keys are provided to a file system client configured to create and store the object at least in part by encrypting each chunk included in the plurality of component chunks using the chunk key provided for that chunk to generated encrypted chunk data, and combining the encrypted chunk data to create and store the object.
1. A method of storing file system data, comprising:
computing a corresponding chunk hash value for each of a plurality of component chunks of file system data associated with an object, wherein a chunk hash value is based on at least a portion of data stored in a component chunk;
determining for the object a primary encryption key, wherein the object is comprised of the plurality of component chunks and the file system data is divided into a plurality of objects, each object of the plurality of objects having a corresponding primary encryption key;
storing the primary encryption key in a file system metadata table;
using the primary encryption key to generate, for each of said component chunks, a corresponding chunk key, wherein the corresponding chunk key is based at least in part on the primary encryption key and the corresponding chunk hash value associated with the corresponding chunk; and
providing chunk keys of the plurality of component chunks associated with the object to a file system client configured to create and store the object at least in part by encrypting each chunk included in the plurality of component chunks using a chunk key provided for that chunk to generate encrypted chunk data, and combining the encrypted chunk data to create and store the object.
2. The method of claim 1 , wherein the primary encryption key is determined based at least in part on data comprising or otherwise associated with the plurality of component chunks.
3. The method of claim 1 , wherein the chunk keys are not stored in file system metadata.
4. The method of claim 1 , further comprising providing to the file system client an identification of the plurality of component chunks to be included in the object.
5. The method of claim 1 , wherein the plurality of component chunks of file system data comprise at least a part of a file.
6. The method of claim 5 , further comprising receiving a request to store the file, the request including data identifying the plurality of component chunks as being associated with the file.
7. The method of claim 1 , further comprising receiving a request to access a file with which the plurality of component chunks are associated.
8. The method of claim 7 , further comprising providing in response to the request a locator to be used to retrieve the object, and for each chunk a corresponding offset within the object and a corresponding chunk key to be used to decrypt the chunk.
9. A system, comprising:
a communication interface; and
a processor coupled to the communication interface and configured to:
compute a corresponding chunk hash value for each of a plurality of component chunks of file system data associated with an object, wherein a chunk hash value is based on at least a portion of data stored in a component chunk;
determine for the object a primary encryption key, wherein the object is comprised of the plurality of component chunks and the file system data is divided into a plurality of objects, each object of the plurality of objects having a corresponding primary encryption key;
store the primary encryption key in a file system metadata table;
use the primary encryption key to generate, for each of said component chunks, a corresponding chunk key, wherein the corresponding chunk key is based at least in part on the primary encryption key and the corresponding chunk hash value associated with the corresponding chunk; and
provide chunk keys of the plurality of component chunks associated with the object, via the communication interface, to a file system client configured to create and store the object at least in part by encrypting each chunk included in the plurality of component chunks using a chunk key provided for that chunk to generate encrypted chunk data, and combining the encrypted chunk data to create and store the object.
10. The system of claim 9 , wherein the primary encryption key is determined based at least in part on data comprising or otherwise associated with the plurality of component chunks.
11. The system of claim 9 , wherein the chunk keys are not stored in file system metadata.
12. The system of claim 9 , wherein the processor is further configured to provide to the file system client an identification of the plurality of component chunks to be included in the object.
13. The system of claim 9 , wherein the plurality of component chunks of file system data comprise at least a part of a file.
14. The system of claim 13 , wherein the processor is further configured to receive a request to store the file, the request including data identifying the plurality of component chunks as being associated with the file.
15. The system of claim 9 , wherein the processor is further configured to receive a request to access a file with which the plurality of component chunks are associated; and to provide in response to the request a locator to be used to retrieve the object, and for each chunk a corresponding offset within the object and a corresponding chunk key to be used to decrypt the chunk.
16. A computer program product to store file system data, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
computing a corresponding chunk hash value for each of a plurality of component chunks of file system data associated with an object, wherein a chunk hash value is based on at least a portion of data stored in a component chunk;
determining for the object a primary encryption key, wherein the object is comprised of the plurality of component chunks and the file system data is divided into a plurality of objects, each object of the plurality of objects having a corresponding primary encryption key;
storing the primary encryption key in a file system metadata table;
using the primary encryption key to generate, for each of said component chunks, a corresponding chunk key, wherein the corresponding chunk key is based at least in part on the primary encryption key and the corresponding chunk hash value associated with the corresponding chunk; and
providing chunk keys of the plurality of component chunks associated with the object to a file system client configured to create and store the object at least in part by encrypting each chunk included in the plurality of component chunks using a chunk key provided for that chunk to generate encrypted chunk data, and combining the encrypted chunk data to create and store the object.