Page 1:TrueCrypt 6.1--Tried And Tested
Page 2:TrueCrypt 6.1 Features And Testing Considerations
Page 3:Commencing Encryption For A Windows System
Page 4:Encryption Algorithm, Performance, Rescue Disc
Page 5:Wipe Blanks, Pretest, And Encryption
Page 6:First-Start, Limitations, Decrypting
Page 7:Test Setup And Benchmarks
Page 8:PCMark Vantage Benchmarks
Page 9:Application Benchmarks
Page 10:Results: MobileMark 07
Wipe Blanks, Pretest, And Encryption
This feature probably seems like overkill, but if you don’t want any traces to remain on a hard drive and only work with the encrypted data, it is important. The procedure effectively removes existing file fragments that may still be on a hard drive from previous system installations. Select 3-pass, 7-pass, or a solid 35-pass wiping of unused areas and these will systematically be overwritten.
Before actually encrypting your system, TrueCrypt verifies that the system boots correctly using the boot loader, not yet using encryption nor the password.
Once restarted, the actual encryption process may begin.
Our test system, a Dell Latitude D610, was equipped with a 45 nm Core 2 Duo Penryn T9500 processor (2.6 GHz) and a brand new Western Digital WD5000BEVT 500 GB Scorpio drive, one of the fastest mainstream drives available today. The entire encryption process using AES took eight hours, during which we could keep using the system (though we did not do much). The process takes place in the background and only consumes CPU resources during system idle times. This obviously means that working with the system intensively results in a longer encryption period.
- TrueCrypt 6.1--Tried And Tested
- TrueCrypt 6.1 Features And Testing Considerations
- Commencing Encryption For A Windows System
- Encryption Algorithm, Performance, Rescue Disc
- Wipe Blanks, Pretest, And Encryption
- First-Start, Limitations, Decrypting
- Test Setup And Benchmarks
- PCMark Vantage Benchmarks
- Application Benchmarks
- Results: MobileMark 07