Talk:Filesystem-level encryption

message: Wikipedia appears to have a de facto standard of spelling out "file system" as separate words instead of "filesystem"; however, I don't think the title of this article (or any links) should follow that, as the phrase "file system-level encryption" could be interpreted as "system-level file encryption" which is not quite right – file system is a precise technical term. Opinions? -- intgr 03:29, 16 December 2006 (UTC)
replies: text: Seems like a pragmatic solution. Open4D (talk) 07:10, 29 November 2013 (UTC)
thread_title: Naming

message: "Given the coarsely stated differentiation between "filesystem-level encryption" and "cryptographic file systems," it should be clear to all but the novice that the former does not in any way implement automatic encryption, which—one imagines—is what the user would expect. Nor is a file kept encrypted automatically and updated, fully encrypted, in place: indeed, one must bodily decrypt, modify, and encrypt in order to make the least change. Anyone can use a third-party utility to encrypt this file or that folder on demand, so packaging that capability within the file browser and terming it "filesystem-level encryption" is, at best, deceptive. The differentiation indicated heretofore, that is, whether metadata is or is not encrypted, merely obfuscates the issue. Windows, in fact, does not provide any capability resembling automatic encryption: to this extent, at least, the oft-ballyhooed "filesystem-level encryption" is merely a minor convenience that frees the user from having to install a third-party encryption application."
: [User:Intgr] responded with "(revert POV/weasel blurb; no source cited for claiming that general-purpose FSes don't do in-place updates; Windows does provide 'automatic' encryption with folder attributes)."
:: We may be splitting hairs here, but let's clarify: Windows implements what I'd call "conditional filesystem-level encryption".  The encryption by EFS is entirely automated, not requiring any user intervention once it's initially configured, and it is transparent to all applications except those that explicitly implement the Backup APIs.  That said, it's conditional in that the EFS component driver will encrypt files only if it detects that either (a) the folder has the Encrypted attribute enabled, or (b) the user application (e.g. Windows Explorer, CIPHER.EXE) has passed an explicit flag to request that the file be created encrypted.  Once a file is encrypted, it is kept encrypted automatically and updated, fully encrypted, in place (unless the user explicitly requests that the file be decrypted).
:: Question to the original poster (69.140.68.72): to what other mistakenly-labelled "filesystem-level encryption" application are you referring?  —Preceding unsigned comment added by ParanoidMike (talk • contribs) 22:07, August 27, 2007 (UTC) 
: Maybe the problem with "differentiation between filesystem-level encryption and cryptographic file systems" would be mitigated by my suggestions at Talk:Disk encryption#File & disk encryption article restructuring.  Part of my suggestion is that this Filesystem-level encryption article would become just a redirect.  Open4D (talk) 07:16, 29 November 2013 (UTC)
thread_title: Re: reverted edit by 69.140.68.72