Encrypting a file may not guarantee that it remains
encrypted forever. For example, some applications, when
editing and saving files, will delete the original file and then
recreate it in the same place. If the application is unaware of
encryption, the protection will be lost. The workaround is to
encrypt the folder containing the file rather than the file itself.
If you change the ownership of a file (as described in ???Set Permissions for a
File or Folder,??? earlier in this chapter) and the file is encrypted, the encryption
will remain active for the original owner and creator of the file, even
though that user no longer technically ???owns??? the file.
Since all users need to access files in certain folders, such as the \Windows
and \Windows\System folders, Windows won??™t let you encrypt files and system
folders or the root directories of any drives.
Compression, another feature of the NTFS filesystem,
reduces the amount of space consumed by a file or folder.
The rules that apply to compression are more or less the
same as those that apply to encryption. But you cannot
simultaneously use encryption and compression on any
object; turn on one option in the Properties window, and
Windows will turn the other off. See ???If in Doubt, Throw It
Out,??? in Chapter 5, for more information.
Permissions and Security | 473
Users and
Security
Highlight encrypted files in Windows Explorer
By default, Windows Explorer visually differentiates encrypted files, which
can be a very handy way to keep track of the scope of your encryption.
Pages:
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660