Filesystem-level encryption: Difference between revisions

Revision as of 06:13, 19 March 2012

Revision as of 18:54, 14 August 2012

Line 9:

==General-purpose file systems with encryption==

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 cancman 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 about the storage pool is still stored in the clear so it is possible to determine how many filesystems (datasets) are available in the pool and even which ones are encrypted but not what the content of the stored files or directories are.

Line 21:

* [[List of cryptographic file systems]]

* [[Disk encryption]]

==External links==

*[http://www.securencrypt.com File encryption software based on a patented algorithm]

[[Category:Disk encryption]]