Windows 2000 does not encrypt compressed, read-only, nor system files even though encryption can be selected for such files:
From Windows Explorer, right click a file or folder for its Properties.
The General tab will have an Advanced... button if the drive is NTFS.
Click it. Select Encrypt contents to secure data.
Notice Compress contents to save disk space
is automatically unselected when Encrypt is selected
because Windows 2000 does not encrypt compressed files.
To convert files into ciphertext, Microsoft Windows 2000 uses DESX, a modified version of DES
.
- 40-bits in International editions using
Microsoft Basic Cryptographic Provider v1.0
- 56-bits in the North American edition using
Microsoft Enhanaced Crypographic Provider v1.0
To make Windows 2000 encrypt with three 128 bit keys, enable Triple DES (also called TDES or 3DES or DES3),
install the hardened
"High Encryption Pack add-on for Windows 2000"
.
This can be used by all countries except those
embargoed and
debarred or otherwise
controlled by various agencies of the US government.
Use the CIPHER.EXE utility to /Encrypt, /Decrypt /All files or /Specified directories in NTFS partitions.
For a full list of options, including /I to Ignore errors,
enter this at a command prompt:
cipher /?
During file encryption, Windows 2000 generates a random number called the
FEK (File Encryption Key) using the file owner's public key.
If the user does not have a key pair, one is generated on the fly and stored in the user's profile.
The encrypted FEK is stored in the DDF (Data Decryption Field) for the file.
Another copy of the FEK is encrypted with the public key of one or more recovery agents
and stored in the DRF (Data Recovery Field) for the file.
If the user's machine is not a member of a domain, the Local Administrator account is the designated recovery agent for all files encrypted on that machine.
(this account's key pair is also automatically generated).
In a domain environment, the default recovery agent is the Domain Administrator account.
(This can, and typically should, be customized via group policy)
So before you encrypt, modify the Recovery Agent's default setup in which
the Administrator account is the agent for locally encrypted data.
Reassign the Recovery Agent role to a separate domain account so that in the event of failure,
the designated domain account-based Recovery Agent can recover the data.
The LSAS (Local Security Authority Server) decrypts files by first decrypting the FEK in the DDF
using the owner's private key or decrypting the recovery agent's FEK from the DRF.
The decrypted FEK is then used to decrypt the encrypted file.
This should be transparent process.
Encrypted files are not indexed by the Index Service.
Since data is still sent over a network in clear text,
allowing it to be captured as it travels over the network,
also use IPSec to secure network communications.
If an encrypted file is copied to a diskette or other non-NTFS (FAT32) volume,
the file is automatically unencrypted into clear text!
If a file is moved from an EFS file, it is left decrypted.
efsinfo.exe from the
Resource Kit Security.cab file
lists for encrypted folders and files their
/Certificate thumbnail and /Recovery agent: