Windows-based file encryption may corrupt data

Windows-based file encryption may corrupt data



I'm not necessarily a fan of the Encryption File System (EFS) built into Windows. However, I do agree that encrypting stored data is a valid means to improve security in most environments. Assuming you take the time to properly configure your recovery agents and store your decryption keys on removable media (such as USB memory sticks or at least a floppy), there are a few additional caveats you need to know to prevent catastrophe with Windows EFS.

EFS is a native feature via NTFS of Windows 2000, Windows XP and Windows 2003. However, EFS employs a different encryption mechanism depending on the version of Windows employed. Windows 2000 uses DES. Windows XP pre-SP1 uses 3DES. Windows XP SP1+ and Windows 2003 use AES. Windows 2000 can only decrypt files using DES. Windows XP pre-SP1 can decrypt files using DES or 3DES. Windows XP SP1+ and Windows 2003 can decrypt files using DES, 3DES or AES. If you have an environment where different versions of these platforms are deployed, you can easily get yourself in a situation where you encrypt a file using one platform and you need to decrypt that same file from another platform. The problem is, attempting to use a "lower end" decryption scheme to decipher a file encrypted using a "higher end" scheme can result not just in a failure to extract the original file, but a corruption of the file so that it cannot be decrypted even using the correct encryption mechanism. In other words, the attempt to decrypt actually damages

    Requires Free Membership to View

    Login

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

the file rather than just failing.

Fortunately, there is a work around for this problem, but it requires you to elect to use the lowest common denominator in terms of encryption strength across all platforms. A simple Registry edit can change the default behavior of each platform to use a shared common encryption scheme. For details on making this change to your systems, see the Knowledge Base article #329741, EFS files appear corrupted when you open them.

About the author
James Michael Stewart is a partner and researcher for ITinfopros, a technology-focused writing and training organization.

For more information, visit these other resources:

This was first published in April 2003

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Back to top