Filesystem-level encryption: Difference between revisions

Content deleted Content added
General-purpose file systems with encryption: Rewrote half the paragraph, using less conversational tone ("this, and even that" > "this, including that") and more universal technical language ("in the clear" > "plaintext").
Line 11:
Unlike cryptographic file systems or full disk encryption, general-purpose file systems that include filesystem-level encryption do not typically encrypt file system [[metadata]], such as the directory structure, file names, sizes or modification timestamps. This can be problematic if the metadata itself needs to be kept confidential. In other words, if files are stored with identifying file names, anyone who has access to the physical disk can know which documents are stored on the disk, although not the contents of the documents.
 
One exception to this is the encryption support being added to the [[ZFS]] filesystem. Filesystem metadata such as filenames, ownership, ACLs, extended attributes are all stored encrypted on disk. The [[ZFS]] metadata aboutrelating to the storage pool is still stored in the clear[[plaintext]], so it is possible to determine how many filesystems (datasets) are available in the pool, and evenincluding which ones are encrypted. but not what theThe content of the stored files orand directories areremain encrypted.
 
==Cryptographic file systems==