Free open source on-the-fly encryption software
Angaben gemäß § 5 TMG:
André Pilarczyk
Vorster Str. 464a
41169 Mönchengladbach
Kontakt:
| Telefon: | |
| E-Mail: | info@truecrypt71a.com |
Verantwortlich für den Inhalt nach § 55 Abs. 2 RStV:
André Pilarczyk
Vorster Straße 464a
41169 Mönchengladbach
Quellenangaben für die verwendeten Bilder und Grafiken:
TrueCrypt
Quelle: http://www.e-recht24.de
Haftung für Inhalte
Als Diensteanbieter sind wir gemäß § 7 Abs.1 TMG für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Nach §§ 8 bis 10 TMG sind wir als Diensteanbieter jedoch nicht verpflichtet, übermittelte oder gespeicherte fremde Informationen zu überwachen oder nach Umständen zu forschen, die auf eine rechtswidrige Tätigkeit hinweisen. Verpflichtungen zur Entfernung oder Sperrung der Nutzung von Informationen nach den allgemeinen Gesetzen bleiben hiervon unberührt. Eine diesbezügliche Haftung ist jedoch erst ab dem Zeitpunkt der Kenntnis einer konkreten Rechtsverletzung möglich. Bei Bekanntwerden von entsprechenden Rechtsverletzungen werden wir diese Inhalte umgehend entfernen.
Haftung für Links
Unser Angebot enthält Links zu externen Webseiten Dritter, auf deren Inhalte wir keinen Einfluss haben. Deshalb können wir für diese fremden Inhalte auch keine Gewähr übernehmen. Für die Inhalte der verlinkten Seiten ist stets der jeweilige Anbieter oder Betreiber der Seiten verantwortlich. Die verlinkten Seiten wurden zum Zeitpunkt der Verlinkung auf mögliche Rechtsverstöße überprüft. Rechtswidrige Inhalte waren zum Zeitpunkt der Verlinkung nicht erkennbar. Eine permanente inhaltliche Kontrolle der verlinkten Seiten ist jedoch ohne konkrete Anhaltspunkte einer Rechtsverletzung nicht zumutbar. Bei Bekanntwerden von Rechtsverletzungen werden wir derartige Links umgehend entfernen.
Urheberrecht
Die durch die Seitenbetreiber erstellten Inhalte und Werke auf diesen Seiten unterliegen dem deutschen Urheberrecht. Die Vervielfältigung, Bearbeitung, Verbreitung und jede Art der Verwertung außerhalb der Grenzen des Urheberrechtes bedürfen der schriftlichen Zustimmung des jeweiligen Autors bzw. Erstellers. Downloads und Kopien dieser Seite sind nur für den privaten, nicht kommerziellen Gebrauch gestattet. Soweit die Inhalte auf dieser Seite nicht vom Betreiber erstellt wurden, werden die Urheberrechte Dritter beachtet. Insbesondere werden Inhalte Dritter als solche gekennzeichnet. Sollten Sie trotzdem auf eine Urheberrechtsverletzung aufmerksam werden, bitten wir um einen entsprechenden Hinweis. Bei Bekanntwerden von Rechtsverletzungen werden wir derartige Inhalte umgehend entfernen.
We have not implemented any ‘backdoor’ in TrueCrypt (and will never implement any even if asked to do so by a government agency), because it would defeat the purpose of the software. TrueCrypt does not allow decryption of data without knowing the correct password or key. We cannot recover your data because we do not know and cannot determine the password you chose or the key you generated using TrueCrypt. The only way to recover your files is to try to “crack” the password or the key, but it could take thousands or millions of years (depending on the length and quality of the password or keyfiles, on the software/hardware performance, algorithms, and other factors). If you find this hard to believe, consider the fact that even the FBI was not able to decrypt a TrueCrypt volume after a year of trying.
Yes. The first chapter, Beginner’s Tutorial, in the TrueCrypt User Guide contains screenshots and step-by-step instructions on how to create, mount, and use a TrueCrypt volume.
Yes, see the chapter System Encryption in the TrueCrypt User Guide.
Yes, TrueCrypt-encrypted volumes are like normal disks. You provide the correct password (and/or keyfile) and mount (open) the TrueCrypt volume. When you double click the icon of the video file, the operating system launches the application associated with the file type – typically a media player. The media player then begins loading a small initial portion of the video file from the TrueCrypt-encrypted volume to RAM (memory) in order to play it. While the portion is being loaded, TrueCrypt is automatically decrypting it (in RAM). The decrypted portion of the video (stored in RAM) is then played by the media player. While this portion is being played, the media player begins loading another small portion of the video file from the TrueCrypt-encrypted volume to RAM (memory) and the process repeats.
The same goes for video recording: Before a chunk of a video file is written to a TrueCrypt volume, TrueCrypt encrypts it in RAM and then writes it to the disk. This process is called on-the-fly encryption/decryption and it works for all file types (not only for video files).
Yes, it will. We will never create a commercial version of TrueCrypt, as we believe in open-source and free security software.
As the source code for TrueCrypt is publicly available, independent researchers can verify that the source code does not contain any security flaw or secret ‘backdoor’. If the source code were not available, reviewers would need to reverse-engineer the executable files. However, analyzing and understanding such reverse-engineered code is so difficult that it is practicallyimpossible to do (especially when the code is as large as the TrueCrypt code).
Remark: A similar problem also affects cryptographic hardware (for example, a self-encrypting storage device). It is very difficult to reverse-engineer it to verify that it does not contain any security flaw or secret ‘backdoor’.
Yes. In fact, the source code is constantly being reviewed by many independent researchers and users. We know this because many bugs and several security issues have been discovered by independent researchers (including some well-known ones) while reviewing the source code.
Yes, they can. In addition to reviewing the source code, independent researchers can compile the source code and compare the resulting executable files with the official ones. They may find some differences (for example, timestamps or embedded digital signatures) but they can analyze the differences and verify that they do not form malicious code.
You have two options:
Yes. The entire file system within a TrueCrypt volume is encrypted (including file names, folder names, and contents of every file). This applies to both types of TrueCrypt volumes – i.e., to file containers (virtual TrueCrypt disks) and to TrueCrypt-encrypted partitions/devices.
Yes. Increase in encryption/decryption speed is directly proportional to the number of cores/processors your computer has. For more information, please see the chapter Parallelization in the documentation.
Yes, since TrueCrypt uses pipelining and parallelization. For more information, please see the chapters Pipelining and Parallelization in the documentation.
Yes. For more information, please see the chapter Hardware Acceleration in the documentation.
Yes, it is (as of TrueCrypt 6.0). For more information, please see the section Hidden Operating System in the documentation.
Yes, TrueCrypt volumes are independent of the operating system. You will be able to mount your TrueCrypt volume on any computer on which you can run TrueCrypt (see also the question ‘Can I use TrueCrypt on Windows if I do not have administrator privileges?‘).
Before you unplug or turn off the device, you should always dismount the TrueCrypt volume in TrueCrypt first, and then perform the ‘Eject‘ operation if available (right-click the device in the ‘Computer‘ or ‘My Computer‘ list), or use the ‘Safely Remove Hardware‘ function (built in Windows, accessible via the taskbar notification area). Otherwise, data loss may occur.
See the section Hidden Operating System in the documentation.
See the chapter Plausible Deniability in the documentation.
Yes, TrueCrypt volumes are independent of the operating system. However, you need to make sure your operating system installer does not format the partition where your TrueCrypt volume resides.
Note: If the system partition/drive is encrypted and you want to reinstall or upgrade Windows, you need to decrypt it first (selectSystem > Permanently Decrypt System Partition/Drive). However, a running operating system can be updated (security patches, service packs, etc.) without any problems even when the system partition/drive is encrypted.
Generally, yes. However, before upgrading, please read the release notes for all versions of TrueCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the release notes.
Generally, you can upgrade to the latest version without decrypting the system partition/drive (just run the TrueCrypt installer and it will automatically upgrade TrueCrypt on the system). However, before upgrading, please read the release notes for all versions of TrueCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the release notes. Note that this FAQ answer is also valid for users of a hidden operating system. Also note that you cannot downgrade TrueCrypt if the system partition/drive is encrypted.
Yes (as of TrueCrypt 6.1). To do so, boot the encrypted system, start TrueCrypt, select Settings > System Encryption, enable the option ‘Do not show any texts in the pre-boot authentication screen‘ and click OK. Then, when you start the computer, no texts will be displayed by the TrueCrypt boot loader (not even when you enter the wrong password). The computer will appear to be “frozen” while you can type your password. It is, however, important to note that if the adversary can analyze the content of the hard drive, he can still find out that it contains the TrueCrypt boot loader.
Yes (as of TrueCrypt 6.1). To do so, boot the encrypted system, start TrueCrypt, select Settings > System Encryption, enable the option ‘Do not show any texts in the pre-boot authentication screen‘ and enter the fake error message in the corresponding field (for example, the “Missing operating system” message, which is normally displayed by the Windows boot loader if it finds no Windows boot partition). It is, however, important to note that if the adversary can analyze the content of the hard drive, he can still find out that it contains the TrueCrypt boot loader.
Yes. To do so, follow these steps:
For more information, see the chapter System Favorite Volumes.
Yes. To do so, follow these steps:
Then, when you log on to Windows, you will be asked for the volume password (and/or keyfiles) and if it is correct, the volume will be mounted.
Alternatively, if the volumes are partition/device-hosted and if you do not need to mount them to particular drive letters every time, you can follow these steps:
Note: TrueCrypt will not prompt you for a password if you have enabled caching of the pre-boot authentication password (Settings > ‘System Encryption‘) and the volumes use the same password as the system partition/drive.
Yes. For example, if you have a TrueCrypt container on a USB flash drive and you want TrueCrypt to mount it automatically when you insert the USB flash drive into the USB port, follow these steps:
Then, when you insert the USB flash drive into the USB port, you will be asked for the volume password (and/or keyfiles) (unless it is cached) and if it is correct, the volume will be mounted.
Note: TrueCrypt will not prompt you for a password if you have enabled caching of the pre-boot authentication password (Settings > ‘System Encryption‘) and the volume uses the same password as the system partition/drive.
Yes. Select Settings > ‘System Encryption‘ and enable the following option: ‘Cache pre-boot authentication password in driver memory‘.
Yes. This can be achieved by running TrueCrypt in portable mode under BartPE or in a similar environment. BartPE stands for “Bart’s Preinstalled Environment”, which is essentially the Windows operating system prepared in a way that it can be entirely stored on and booted from a CD/DVD (registry, temporary files, etc., are stored in RAM – hard drive is not used at all and does not even have to be present). The freeware Bart’s PE Builder can transform a Windows XP installation CD into a BartPE CD. Note that you do not even need any special TrueCrypt plug-in for BartPE. Follow these steps:
Note: You may also want to consider creating a hidden operating system (see the section Hidden Operating System in the documentation). See also the chapter Plausible Deniability.
Yes, TrueCrypt supports all keyboard layouts.
Yes. You can write data to the decoy system partition anytime without any risk that the hidden volume will get damaged (because the decoy system is not installed within the same partition as the hidden system). For more information, see the section Hidden Operating System in the documentation.
See the chapter ‘Using TrueCrypt Without Administrator Privileges‘ in the documentation.
No.
See the section Encryption Scheme (chapter Technical Details) in the documentation.
Yes, but the following conditions must be met:
Yes, see the chapter Portable Mode in the TrueCrypt User Guide.
No. Those programs use TPM to protect against attacks that require the attacker to have administrator privileges, or physical access to the computer, and the attacker needs you to use the computer after such an access. However, if any of these conditions is met, it is actually impossible to secure the computer (see below) and, therefore, you must stop using it (instead of relying on TPM).
If the attacker has administrator privileges, he can, for example, reset the TPM, capture the content of RAM (containing master keys) or content of files stored on mounted TrueCrypt volumes (decrypted on the fly), which can then be sent to the attacker over the Internet or saved to an unencrypted local drive (from which the attacker might be able to read it later, when he gains physical access to the computer).
If the attacker can physically access the computer hardware (and you use it after such an access), he can, for example, attach a malicious component to it (such as a hardware keystroke logger) that will capture the password, the content of RAM (containing master keys) or content of files stored on mounted TrueCrypt volumes (decrypted on the fly), which can then be sent to the attacker over the Internet or saved to an unencrypted local drive (from which the attacker might be able to read it later, when he gains physical access to the computer again).
The only thing that TPM is almost guaranteed to provide is a false sense of security (even the name itself, “Trusted Platform Module”, is misleading and creates a false sense of security). As for real security, TPM is actually redundant (and implementing redundant features is usually a way to create so-called bloatware).
For more information, please see the sections Physical Security and Malware in the documentation.
No. TrueCrypt automatically dismounts all mounted TrueCrypt volumes on system shutdown/restart.
File containers are normal files so you can work with them as with any normal files (file containers can be, for example, moved, renamed, and deleted the same way as normal files). Partitions/drives may be better as regards performance. Note that reading and writing to/from a file container may take significantly longer when the container is heavily fragmented. To solve this problem, defragment the file system in which the container is stored (when the TrueCrypt volume is dismounted).
See the chapter How to Back Up Securely in the documentation.
See the question ‘Is it possible to change the file system of an encrypted volume?‘
Yes, when mounted, TrueCrypt volumes can be formatted as FAT12, FAT16, FAT32, NTFS, or any other file system. TrueCrypt volumes behave as standard disk devices so you can right-click the device icon (for example in the ‘Computer‘ or ‘My Computer‘ list) and select ‘Format‘. The actual volume contents will be lost. However, the whole volume will remain encrypted. If you format a TrueCrypt-encrypted partition when the TrueCrypt volume that the partition hosts is not mounted, then the volume will be destroyed, and the partition will not be encrypted anymore (it will be empty).
Yes. However, if you need to mount a TrueCrypt volume that is stored on a read-only medium (such as a CD or DVD) under Windows 2000, the file system within the TrueCrypt volume must be FAT (Windows 2000 cannot mount an NTFS file system on read-only media).
Yes, the password change dialog works both for standard and hidden volumes. Just type the password for the hidden volume in the ‘Current Password’ field of the ‘Volume Password Change’ dialog.
Remark: TrueCrypt first attempts to decrypt the standard volume header and if it fails, it attempts to decrypt the area within the volume where the hidden volume header may be stored (if there is a hidden volume within). In case it is successful, the password change applies to the hidden volume. (Both attempts use the password typed in the ‘Current Password’ field.)
No, TrueCrypt never uses an output of a hash function (nor of a HMAC algorithm) directly as an encryption key. See the section Header Key Derivation, Salt, and Iteration Count in the documentation for more information.
The DVD burning software you use should allow you to select the format of the DVD. If it does, select the UDF format (ISO format does not support files larger than 2 GB).
Yes, TrueCrypt volumes behave like real physical disk devices, so it is possible to use any filesystem checking/repairing/defragmenting tools on the contents of a mounted TrueCrypt volume.
Yes, it does. Note: 64-bit versions of Windows load only drivers that are digitally signed with a digital certificate issued by a certification authority approved for issuing kernel-mode code signing certificates. TrueCrypt complies with this requirement (the TrueCrypt driver is digitally signed with the digital certificate of the TrueCrypt Foundation, which was issued by the certification authority GlobalSign).
Yes, TrueCrypt volumes are fully cross-platform.
Yes, see the chapter Supported Operating Systems in the TrueCrypt User Guide.
Yes.
In encrypted data, one corrupted bit usually corrupts the whole ciphertext block in which it occurred. The ciphertext block size used by TrueCrypt is 16 bytes (i.e., 128 bits). The mode of operation used by TrueCrypt ensures that if data corruption occurs within a block, the remaining blocks are not affected. See also the question ‘What do I do when the encrypted filesystem on my TrueCrypt volume is corrupted?
File system within a TrueCrypt volume may become corrupted in the same way as any normal unencrypted file system. When that happens, you can use filesystem repair tools supplied with your operating system to fix it. In Windows, it is the ‘chkdsk‘ tool. TrueCrypt provides an easy way to use this tool on a TrueCrypt volume: Right-click the mounted volume in the main TrueCrypt window (in the drive list) and from the context menu select ‘Repair Filesystem‘.
Yes. Note that there is no “backdoor” implemented in TrueCrypt. However, there is a way to “reset” volume passwords/keyfiles and pre-boot authentication passwords. After you create a volume, back up its header to a file (select Tools -> Backup Volume Header) before you allow a non-admin user to use the volume. Note that the volume header (which is encrypted with a header key derived from a password/keyfile) contains the master key with which the volume is encrypted. Then ask the user to choose a password, and set it for him/her (Volumes -> Change Volume Password); or generate a user keyfile for him/her. Then you can allow the user to use the volume and to change the password/keyfiles without your assistance/permission. In case he/she forgets his/her password or loses his/her keyfile, you can “reset” the volume password/keyfiles to your original admin password/keyfiles by restoring the volume header from the backup file (Tools -> Restore Volume Header).
Similarly, you can reset a pre-boot authentication password. To create a backup of the master key data (that will be stored on a TrueCrypt Rescue Disk and encrypted with your administrator password), select ‘System‘ > ‘Create Rescue Disk‘. To set a user pre-boot authentication password, select ‘System‘ > ‘Change Password‘. To restore your administrator password, boot the TrueCrypt Rescue Disk, select ‘Repair Options‘ > ‘Restore key data‘ and enter your administrator password.
Note: It is not required to burn each TrueCrypt Rescue Disk ISO image to a CD/DVD. You can maintain a central repository of ISO images for all workstations (rather than a repository of CDs/DVDs). For more information see the section Command Line Usage (option /noisocheck).
Provided that you comply with the terms and conditions of the TrueCrypt License, you can install and run TrueCrypt free of charge on an arbitrary number of your computers.
Please see the chapter ‘Sharing over Network‘ in the TrueCrypt User Guide.
Please see the chapter ‘Sharing over Network‘ in the TrueCrypt User Guide.
Please see the chapter ‘Sharing over Network‘ in the TrueCrypt User Guide.
Yes, to free the drive letter follow these steps:
Yes, but you will need to remove the drive letter assigned to the device. For information on how to do so, see the question ‘I encrypted a non-system partition, but its original drive letter is still visible in the ‘My Computer’ list.‘
Please see the section ‘How to Remove Encryption‘ in the TrueCrypt User Guide.
Please see the section ‘Volume Mounted as Removable Medium‘ in the TrueCrypt User Guide.
Yes, the documentation is contained in the file TrueCrypt User Guide.pdf that is included in all official TrueCrypt distribution packages. Note that you do not have to install TrueCrypt to obtain the PDF documentation. Just run the self-extracting installation package and then select Extract (instead of Install) on the second page of the TrueCrypt Setup wizard. Also note that when you do install TrueCrypt, the PDF documentation is automatically copied to the folder to which TrueCrypt is installed, and is accessible via the TrueCrypt user interface (by pressing F1 or choosing Help > User’s Guide).
Remark: to “wipe” = to securely erase; to overwrite sensitive data in order to render them unrecoverable.
If you believe that an adversary will be able to decrypt the volume (for example that he will make you reveal the password), then the answer is yes. Otherwise, it is not necessary, because the volume is entirely encrypted.
Please see the section Encryption Scheme (chapter Technical Details) in the documentation.
[1] U.S. Committee on National Security Systems (CNSS), National Policy on the Use of the Advanced Encryption Standard (AES) to Protect National Security Systems and National Security Information, CNSS Policy No. 15, Fact Sheet No. 1, June 2003, available at http://csrc.nist.gov/groups/STM/cmvp/documents/CNSS15FS.pdf.
[2] C. E. Shannon, Communication Theory of Secrecy Systems, Bell System Technical Journal, v. 28, n. 4, 1949
[3] NIST, Advanced Encryption Standard (AES), Federal Information Processing Standards Publication 197, November 26, 2001, available at http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf.
[4] J. Nechvatal, E. Barker, L. Bassham, W. Burr, M. Dworkin, J. Foti, E. Roback, NIST, Report on the Development of the Advanced Encryption Standard (AES), October 2, 2000, Journal of Research of the National Institute of Standards and Technology, Vol. 106, No. 3, May-June 2001, available at http://nvl.nist.gov/pub/nistpubs/jres/106/3/j63nec.pdf.
[5] B. Schneier, J. Kelsey, D. Whiting, D. Wagner, C. Hall, N. Ferguson, T. Kohno, M. Stay, The Twofish Team’s Final Comments on AES Selection, May 15, 2000, available at http://csrc.nist.gov/archive/aes/round2/comments/20000515-bschneier.pdf.
[6] Bruce Schneier, Beyond Fear: Thinking Sensibly About Security in an Uncertain World, Springer, 2003
[7] RSA Laboratories, PKCS #5 v2.0: Password-Based Cryptography Standard, RSA Data Security, Inc. Public-Key Cryptography Standards (PKCS), March 25, 1999, available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-5v2/pkcs5v2-0.pdf.
[8] H. Krawczyk, M. Bellare, R. Canetti, HMAC: Keyed-Hashing for Message Authentication, RFC 2104, February 1997, available at http://www.ietf.org/rfc/rfc2104.txt.
[9] M. Nystrom, RSA Security, Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512, RFC 4231, December 2005, available at http://www.ietf.org/rfc/rfc4231.txt.
[10] Peter Gutmann, Software Generation of Practically Strong Random Numbers, presented at the 1998 Usenix Security Symposium, available at http://www.cs.auckland.ac.nz/~pgut001/pubs/usenix98.pdf.
[11] Carl Ellison, Cryptographic Random Numbers, originally an appendix to the P1363 standard, available athttp://world.std.com/~cme/P1363/ranno.html.
[12] P. Rogaway, Efficient Instantiations of Tweakable Blockciphers and Refinements to Modes OCB and PMAC, Asiacrypt 2004. LNCS vol. 3329. Springer, 2004. Also available at: http://www.cs.ucdavis.edu/~rogaway/papers/offsets.pdf.
[13] J. Kelsey, Twofish Technical Report #7: Key Separation in Twofish, AES Round 2 public comment, April 7, 2000
[14] NIST, Secure Hash Standard, FIPS 180-2, August 1, 2002, available at http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf.
[15] U. Maurer, J. Massey, Cascade Ciphers: The Importance of Being First, Journal of Cryptology, v. 6, n. 1, 1993
[16] Bruce Schneier, Applied Cryptography, Second Edition, John Wiley & Sons, 1996 [17] Peter Gutmann, Secure Deletion of Data from Magnetic and Solid-State Memory, first published in the Sixth USENIX Security Symposium Proceedings, San Jose, California, July 22-25, 1996, available at http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html
[18] Serpent home page: http://www.cl.cam.ac.uk/~rja14/serpent.html.
[19] M. E. Smid, AES Issues, AES Round 2 Comments, May 22, 2000, available athttp://csrc.nist.gov/archive/aes/round2/comments/20000523-msmid-2.pdf.
[20] A. Menezes, P. van Oorschot, S. Vanstone, Handbook of Applied Cryptography, CRC Press, October 1996
[21] International Organization for Standardization (ISO), Information technology – Security techniques – Hash-functions – Part 3: Dedicated hash-functions, ISO/IEC 10118-3:2004, February 24, 2004
[22] NIST, The Keyed-Hash Message Authentication Code (HMAC), Federal Information Processing Standards Publication 198, March 6, 2002, available at http://csrc.nist.gov/publications/fips/fips198/fips-198a.pdf.
[23] RSA Laboratories, PKCS #11 v2.20: Cryptographic Token Interface Standard, RSA Security, Inc. Public-Key Cryptography Standards (PKCS), June 28, 2004, available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20/pkcs-11v2-20.pdf.
[24] Morris Dworkin, Recommendation for Block Cipher Modes of Operation: The XTS-AES Mode for Confidentiality on Storage Devices, NIST Special Publication 800-3E, January 2010, available at http://csrc.nist.gov/publications/nistpubs/800-38E/nist-sp-800-38E.pdf.
It might happen that a TrueCrypt installation package you download from our server was created or modified by an attacker. For example, the attacker could exploit a vulnerability in the server software we use and alter the installation packages stored on the server, or he/she could alter any of the files en route to you.
Therefore, you should always verify the integrity and authenticity of each TrueCrypt distribution package you download or otherwise obtain from any source. In other words, you should always make sure that the file was created by us and it was not altered by an attacker. One way to do so is to verify so-called digital signature(s) of the file.
We currently use two types of digital signatures:
X.509 signatures have the following advantages, in comparison to PGP signatures:
PGP signatures have the following advantages, in comparison to X.509 signatures:
Please note that X.509 signatures are currently available only for the TrueCrypt self-extracting installation packages for Windows. An X.509 digital signature is embedded in each of those files along with the digital certificate of the TrueCrypt Foundation issued by a public certification authority. To verify the integrity and authenticity of a self-extracting installation package for Windows, follow these steps:
If you do not see the above sentence, the file is very likely corrupted. Note: On some obsolete versions of Windows, some of the necessary certificates are missing, which causes the signature verification to fail.
To verify a PGP signature, follow these steps:
The term ‘malware’ refers collectively to all types of malicious software, such as computer viruses, Trojan horses, spyware, or generally any piece of software (including TrueCrypt or an operating system component) that has been altered, prepared, or can be controlled, by an attacker. Some kinds of malware are designed e.g. to log keystrokes, including typed passwords (such captured passwords are then either sent to the attacker over the Internet or saved to an unencrypted local drive from which the attacker might be able to read it later, when he or she gains physical access to the computer). If you use TrueCrypt on a computer infected with any kind of malware, TrueCrypt may become unable to secure data on the computer.* Therefore, you must not use TrueCrypt on such a computer.
It is important to note that TrueCrypt is encryption software, not anti-malware software. It is your responsibility to prevent malware from running on the computer. If you do not, TrueCrypt may become unable to secure data on the computer.
There are many rules that you should follow to help prevent malware from running on your computer. Among the most important rules are the following: Keep your operating system, Internet browser, and other critical software, up-to-date. In Windows XP or later, turn on DEP for all programs.† Do not open suspicious email attachments, especially executable files, even if they appear to have been sent by your relatives or friends (their computers might be infected with malware sending malicious emails from their computers/accounts without their knowledge). Do not follow suspicious links contained in emails or on websites (even if the email/website appears to be harmless or trustworthy). Do not visit any suspicious websites. Do not download or install any suspicious software. Consider using good, trustworthy, anti-malware software.
* In this section (Malware), the phrase “data on the computer” means data on internal and external storage devices/media (including removable devices and network drives) connected to the computer.
† DEP stands for Data Execution Prevention. For more information about DEP, please visit http://support.microsoft.com/kb/875352, http://technet.microsoft.com/en-us/library/cc700810.aspx, and http://windows.microsoft.com/en-US/windows-vista/What-is-Data-Execution-Prevention.
This section presents possible solutions to common problems that you may run into when using TrueCrypt.
Note: If your problem is not listed here, it might be listed in one of the following sections:
Make sure you use the latest stable version of TrueCrypt. If the problem is caused by a bug in an old version of TrueCrypt, it may have already been fixed. Note: Select Help > About to find out which version you use.
PROBLEM:
Writing/reading to/from volume is very slow even though, according to the benchmark, the speed of the cipher that I’m using is higher than the speed of the hard drive.
PROBABLE CAUSE:
This is probably caused by an interfering application.
POSSIBLE SOLUTION:
First, make sure that your TrueCrypt container does not have a file extension that is reserved for executable files (for example, .exe, .sys, or .dll). If it does, Windows and antivirus software may interfere with the container and adversely affect the performance of the volume.
Second, disable or uninstall any application that might be interfering, which usually is antivirus software or automatic disk defragmentation tool, etc. In case of antivirus software, it often helps to turn off real-time (on-access) scanning in the preferences of the antivirus software. If it does not help, try temporarily disabling the virus protection software. If this does not help either, try uninstalling it completely and restarting your computer subsequently.
PROBLEM:
A TrueCrypt volume cannot be mounted; TrueCrypt reports “Incorrect password or not a TrueCrypt volume”.
POSSIBLE CAUSE:
The volume header may have been damaged by a third-party application or malfunctioning hardware component.
POSSIBLE SOLUTIONS:
“%ProgramFiles%\TrueCrypt\TrueCrypt.exe” /q /m recovery /v \Device\Harddisk1\Partition0
PROBLEM:
After successfully mounting a volume, Windows reports “This device does not contain a valid file system” or a similar error.
PROBABLE CAUSE:
The file system on the TrueCrypt volume may be corrupted (or the volume is unformatted).
POSSIBLE SOLUTION:
You can use filesystem repair tools supplied with your operating system to attempt to repair the filesystem on the TrueCrypt volume. In Windows, it is the ‘chkdsk’ tool. TrueCrypt provides an easy way to use this tool on a TrueCrypt volume: First, make a backup copy of the TrueCrypt volume (because the ‘chkdsk’ tool might damage the filesystem even more) and then mount it. Right-click the mounted volume in the main TrueCrypt window (in the drive list) and from the context menu select ‘Repair Filesystem’.
PROBLEM:
When trying to create a hidden volume, its maximum possible size is unexpectedly small (there is much more free space than this on the outer volume).
PROBABLE CAUSES:
POSSIBLE SOLUTIONS:
Solutions Related to Cause 1:
Solution Related to Cause 2:
Solution Related to Cause 3:
PROBLEM:
One of the following problems occurs:
In addition, the following error may be reported: “The process cannot access the file because it is being used by another process.”
PROBABLE CAUSE:
This is probably caused by an interfering application. Note that this is not a bug in TrueCrypt. The operating system reports to TrueCrypt that the device is locked for an exclusive access by an application (so TrueCrypt is not allowed to access it).
POSSIBLE SOLUTION:
It usually helps to disable or uninstall the interfering application, which is usually an anti-virus utility, a disk management application, etc.
PROBLEM:
In the TrueCrypt Boot Loader screen, I’m trying to type my password and/or pressing other keys but the TrueCrypt boot loader is not responding.
PROBABLE CAUSE:
You have a USB keyboard (not a PS/2 keyboard) and pre-boot support for USB keyboards is disabled in your BIOS settings.
POSSIBLE SOLUTION:
You need to enable pre-boot support for USB keyboards in your BIOS settings. To do so, follow the below steps:
Restart your computer, press F2 or Delete (as soon as you see a BIOS start-up screen), and wait until a BIOS configuration screen appears. If no BIOS configuration screen appears, restart (reset) the computer again and start pressing F2 or Delete repeatedly as soon as you restart (reset) the computer. When a BIOS configuration screen appears, enable pre-boot support for USB keyboards. This can typically be done by selecting: Advanced > ‘USB Configuration’ > ‘Legacy USB Support’ (or ‘USB Legacy’) > Enabled. (Note that the word ‘legacy’ is in fact misleading, because pre-boot components of modern versions of MS Windows require this option to be enabled to allow user interaction/control.) Then save the BIOS settings (typically by pressing F10) and restart your computer. For more information, please refer to the documentation for your BIOS/motherboard or contact your computer vendor’s technical support team for assistance.
PROBLEM:
After the system partition/drive is encrypted, the computer cannot boot after it is restarted (it is also impossible to enter the BIOS configuration screen).
PROBABLE CAUSE:
A bug in the BIOS of your computer.
POSSIBLE SOLUTIONS:
OR
PROBLEM:
One of the following problems occurs:
PROBABLE CAUSE:
A bug in the BIOS of your computer.
POSSIBLE SOLUTIONS:
PROBLEM:
When mounting or dismounting a TrueCrypt volume, the system crashes (a ‘blue screen’ error screen appears or the computer abruptly restarts).
OR
Since I installed TrueCrypt, the operating system has been crashing frequently.
POSSIBLE CAUSES:
POSSIBLE SOLUTIONS:
PROBLEM:
When trying to encrypt the system partition/drive, during the pretest, the TrueCrypt Boot Loader always reports that the pre-boot authentication password I entered is incorrect (even though I’m sure it is correct).
POSSIBLE CAUSES:
POSSIBLE SOLUTION:
Note: For other possible solutions to this problem, see the other sections of this chapter.
PROBLEM:
When the system partition/drive is encrypted, the operating system ‘freezes’ for approx. 10-60 seconds every 5-60 minutes (100% CPU usage may co-occur).
PROBABLE CAUSE:
A CPU and/or motherboard issue.
POSSIBLE SOLUTIONS:
PROBLEM:
On Windows 7/Vista (and possibly later versions), the Microsoft Windows Backup tool cannot be used to backup data to a non-system TrueCrypt Volume.
CAUSE:
A bug in the Windows Backup tool.
POSSIBLE SOLUTION:
Note: The above solution does not apply to the Starter and Home editions of Windows 7 (and possibly later versions).
PROBLEM:
The label of a filesystem in a TrueCrypt volume cannot be changed from within the ‘Computer’ window under Windows Vista or a later version of Windows.
CAUSE:
A Windows issue causes the label to be written only to the Windows registry file, instead of being written to the filesystem.
POSSIBLE SOLUTIONS:
PROBLEM:
I cannot encrypt a partition/device because TrueCrypt Volume Creation Wizard says it is in use.
POSSIBLE SOLUTION:
Close, disable, or uninstall all programs that might be using the partition/device in any way (for example an anti-virus utility). If it does not help, right-click the ‘Computer’ (or ‘My Computer’) icon on your desktop and select Manage -> Storage -> Disk Management. Then right-click the partition that you want to encrypt, and click Change Drive Letter and Paths. Then clickRemove and OK. Restart the operating system.
PROBLEM:
When creating a hidden volume, the Wizard reports that the outer volume cannot be locked.
PROBABLE CAUSE:
The outer volume contains files being used by one or more applications.
POSSIBLE SOLUTION:
Close all applications that are using files on the outer volume. If it does not help, try disabling or uninstalling any anti-virus utility you use and restarting the system subsequently.
PROBLEM:
When accessing a file-hosted container shared over a network, “insufficient memory” or “not enough server storage is available” error is reported.
PROBABLE CAUSE:
IRPStackSize in the Windows registry may have been set to a too small value.
POSSIBLE SOLUTION:
Locate the IRPStackSize key in the Windows registry and set it to a higher value. Then restart the system. If the key does not exist in the Windows registry, create it atHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and set its value to 16 or higher. Then restart the system. For more information, see: http://support.microsoft.com/kb/285089/ andhttp://support.microsoft.com/kb/177078/
TrueCrypt License Version 3.0
Software distributed under this license is distributed on an “AS IS” BASIS WITHOUT WARRANTIES OF ANY KIND. THE AUTHORS AND DISTRIBUTORS OF THE SOFTWARE DISCLAIM ANY LIABILITY. ANYONE WHO USES, COPIES, MODIFIES, OR (RE)DISTRIBUTES ANY PART OF THE SOFTWARE IS, BY SUCH ACTION(S), ACCEPTING AND AGREEING TO BE BOUND BY ALL TERMS AND CONDITIONS OF THIS LICENSE. IF YOU DO NOT ACCEPT THEM, DO NOT USE, COPY, MODIFY, NOR (RE)DISTRIBUTE THE SOFTWARE, NOR ANY PART(S) THEREOF.
I. Definitions
1. “This Product” means the work (including, but not limited to, source code, graphics, texts, and accompanying files) made available under and governed by this version of this license (“License”), as may be indicated by, but is not limited to, copyright notice(s) attached to or included in the work.
2. “You” means (and “Your” refers to) an individual or a legal entity (e.g., a non-profit organization, commercial organization, government agency, etc.) exercising permissions granted by this License.
3. “Modification” means (and “modify” refers to) any alteration of This Product, including, but not limited to, addition to or deletion from the substance or structure of This Product, translation into another language, repackaging, alteration or removal of any file included with This Product, and addition of any new files to This Product.
4. “Your Product” means This Product modified by You, or any work You derive from (or base on) any part of This Product. In addition, “Your Product” means any work in which You include any (modified or unmodified) portion of This Product. However, if the work in which you include it is an aggregate software distribution (such as an operating system distribution or a cover CD-ROM of a magazine) containing multiple separate products, then the term “Your Product” includes only those products (in the aggregate software distribution) that use, include, or depend on a modified or unmodified version of This Product (and the term “Your Product” does not include the whole aggregate software distribution). For the purposes of this License, a product suite consisting of two or more products is considered a single product (operating system distributions and cover media of magazines are not considered product suites).
5. “Distribution” means (and “distribute” refers to), regardless of means or methods, conveyance, transfer, providing, or making available of This/Your Product or portions thereof to third parties (including, but not limited to, making This/Your Product, or portions thereof, available for download to third parties, whether or not any third party has downloaded the product, or any portion thereof, made available for download).
II. Use, Copying, and Distribution of This Product
1. Provided that You comply with all applicable terms and conditions of this License, You may make copies of This Product (unmodified) and distribute copies of This Product (unmodified) that are not included in another product forming Your Product (except as permitted under Chapter III). Note: For terms and conditions for copying and distribution of modified versions of This Product, see Chapter III.
2. Provided that You comply with all applicable terms and conditions of this License, You may use This Product freely (see also Chapter III) on any number of computers/systems for non-commercial and/or commercial purposes.
III. Modification, Derivation, and Inclusion in Other Products
1. If all conditions specified in the following paragraphs in this Chapter (III) are met (for exceptions, see Section III.2) and if You comply with all other applicable terms and conditions of this License, You may modify This Product (thus forming Your Product), derive new works from This Product or portions thereof (thus forming Your Product), include This Product or portions thereof in another product (thus forming Your Product, unless defined otherwise in Chapter I), and You may use (for non-commercial and/or commercial purposes), copy, and/or distribute Your Product.
Portions of the source code of Your Product not contained in This Product (e.g., portions added by You in creating Your Product, whether created by You or by third parties) must be available under license(s) that (however, see also Subsection III.1.e) allow(s) anyone to modify and derive new works from the portions of the source code that are not contained in This Product and to use, copy, and redistribute such modifications and/or derivative works. The license(s) must be perpetual, non-exclusive, royalty-free, no-charge, and worldwide, and must not invalidate, weaken, restrict, interpret, amend, modify, interfere with or otherwise affect any part, term, provision, or clause of this License. The text(s) of the license(s) must be included with every copy of Your Product that You make and distribute.
2. You are not obligated to comply with Subsection III.1.d if Your Product is not distributed (i.e., Your Product is available only to You).
IV. Disclaimer of Liability, Disclaimer of Warranty, Indemnification
You expressly acknowledge and agree to the following:
1. IN NO EVENT WILL ANY (CO)AUTHOR OF THIS PRODUCT, OR ANY APPLICABLE INTELLECTUAL-PROPERTY OWNER, OR ANY OTHER PARTY WHO MAY COPY AND/OR (RE)DISTRIBUTE THIS PRODUCT OR PORTIONS THEREOF, AS MAY BE PERMITTED HEREIN, BE LIABLE TO YOU OR TO ANY OTHER PARTY FOR ANY DAMAGES, INCLUDING, BUT NOT LIMITED TO, ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, PUNITIVE, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, CORRUPTION OR LOSS OF DATA, ANY LOSSES SUSTAINED BY YOU OR THIRD PARTIES, A FAILURE OF THIS PRODUCT TO OPERATE WITH ANY OTHER PRODUCT, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR BUSINESS INTERRUPTION), WHETHER IN CONTRACT, STRICT LIABILITY, TORT (INCLUDING, BUT NOT LIMITED TO, NEGLIGENCE) OR OTHERWISE, ARISING OUT OF THE USE, COPYING, MODIFICATION, OR (RE)DISTRIBUTION OF THIS PRODUCT (OR A PORTION THEREOF) OR OF YOUR PRODUCT (OR A PORTION THEREOF), OR INABILITY TO USE THIS PRODUCT (OR A PORTION THEREOF), EVEN IF SUCH DAMAGES (OR THE POSSIBILITY OF SUCH DAMAGES) ARE/WERE PREDICTABLE OR KNOWN TO ANY (CO)AUTHOR, INTELLECTUAL-PROPERTY OWNER, OR ANY OTHER PARTY.
2. THIS PRODUCT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THIS PRODUCT IS WITH YOU. SHOULD THIS PRODUCT PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.
3. THIS PRODUCT MAY INCORPORATE IMPLEMENTATIONS OF CRYPTOGRAPHIC ALGORITHMS THAT ARE REGULATED (E.G., SUBJECT TO EXPORT/IMPORT CONTROL REGULATIONS) OR ILLEGAL IN SOME COUNTRIES. IT IS SOLELY YOUR RESPONSIBILITY TO VERIFY THAT IT IS LEGAL TO IMPORT AND/OR (RE)EXPORT AND/OR USE THIS PRODUCT (OR PORTIONS THEREOF) IN COUNTRIES WHERE YOU INTEND TO USE IT AND/OR TO WHICH YOU INTEND TO IMPORT IT AND/OR FROM WHICH YOU INTEND TO EXPORT IT, AND IT IS SOLELY YOUR RESPONSIBILITY TO COMPLY WITH ANY APPLICABLE REGULATIONS, RESTRICTIONS, AND LAWS.
4. YOU SHALL INDEMNIFY, DEFEND AND HOLD ALL (CO)AUTHORS OF THIS PRODUCT, AND APPLICABLE INTELLECTUAL-PROPERTY OWNERS, HARMLESS FROM AND AGAINST ANY AND ALL LIABILITY, DAMAGES, LOSSES, SETTLEMENTS, PENALTIES, FINES, COSTS, EXPENSES (INCLUDING REASONABLE ATTORNEYS’ FEES), DEMANDS, CAUSES OF ACTION, CLAIMS, ACTIONS, PROCEEDINGS, AND SUITS, DIRECTLY RELATED TO OR ARISING OUT OF YOUR USE, INABILITY TO USE, COPYING, (RE)DISTRIBUTION, IMPORT AND/OR (RE)EXPORT OF THIS PRODUCT (OR PORTIONS THEREOF) AND/OR YOUR BREACH OF ANY TERM OF THIS LICENSE.
V. Trademarks
This License does not grant permission to use trademarks associated with (or applying to) This Product, except for fair use as defined by applicable law and except for use expressly permitted or required by this License. Any attempt otherwise to use trademarks associated with (or applying to) This Product automatically and immediately terminates Your rights under This License and may constitute trademark infringement (which may be prosecuted).
VI. General Terms and Conditions, Miscellaneous Provisions
1. ANYONE WHO USES AND/OR COPIES AND/OR MODIFIES AND/OR CREATES DERIVATIVE WORKS OF AND/OR (RE)DISTRIBUTES THIS PRODUCT, OR ANY PORTION(S) THEREOF, IS, BY SUCH ACTION(S), AGREEING TO BE BOUND BY AND ACCEPTING ALL TERMS AND CONDITIONS OF THIS LICENSE (AND THE RESPONSIBILITIES AND OBLIGATIONS CONTAINED IN THIS LICENSE). IF YOU DO NOT ACCEPT (AND AGREE TO BE BOUND BY) ALL TERMS AND CONDITIONS OF THIS LICENSE, DO NOT USE, COPY, MODIFY, CREATE DERIVATIVE WORKS OF, NOR (RE)DISTRIBUTE THIS PRODUCT, NOR ANY PORTION(S) THEREOF.
2. YOU MAY NOT USE, MODIFY, COPY, CREATE DERIVATIVE WORKS OF, (RE)DISTRIBUTE, OR SUBLICENSE THIS PRODUCT, OR PORTION(S) THEREOF, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE (EVEN IF APPLICABLE LAW GIVES YOU MORE RIGHTS). ANY ATTEMPT (EVEN IF PERMITTED BY APPLICABLE LAW) OTHERWISE TO USE, MODIFY, COPY, CREATE DERIVATIVE WORKS OF, (RE)DISTRIBUTE, OR SUBLICENSE THIS PRODUCT, OR PORTION(S) THEREOF, AUTOMATICALLY AND IMMEDIATELY TERMINATES YOUR RIGHTS UNDER THIS LICENSE AND CAN CONSTITUTE COPYRIGHT INFRINGEMENT (WHICH MAY BE PROSECUTED). ANY CONDITIONS AND RESTRICTIONS CONTAINED IN THIS LICENSE ARE ALSO LIMITATIONS ON THE SCOPE OF THIS LICENSE AND ALSO DEFINE THE SCOPE OF YOUR RIGHTS UNDER THIS LICENSE. YOUR FAILURE TO COMPLY WITH THE TERMS AND CONDITIONS OF THIS LICENSE OR FAILURE TO PERFORM ANY APPLICABLE OBLIGATION IMPOSED BY THIS LICENSE AUTOMATICALLY AND IMMEDIATELY TERMINATES YOUR RIGHTS UNDER THIS LICENSE AND CAN CAUSE OR BE CONSIDERED COPYRIGHT INFRINGEMENT (WHICH MAY BE PROSECUTED). NOTHING IN THIS LICENSE SHALL IMPLY OR BE CONSTRUED AS A PROMISE, OBLIGATION, OR COVENANT NOT TO SUE FOR COPYRIGHT OR TRADEMARK INFRINGEMENT IF YOU DO NOT COMPLY WITH THE TERMS AND CONDITIONS OF THIS LICENSE.
3. This License does not constitute or imply a waiver of any intellectual property rights except as may be otherwise expressly provided in this License. This License does not transfer, assign, or convey any intellectual property rights (e.g., it does not transfer ownership of copyrights or trademarks).
4. Subject to the terms and conditions of this License, You may allow a third party to use Your copy of This Product (or a copy that You make and distribute, or Your Product) provided that the third party explicitly accepts and agrees to be bound by all terms and conditions of this License and the third party is not prohibited from using This Product (or portions thereof) by this License (see, e.g., Section VI.7) or by applicable law. However, You are not obligated to ensure that the third party accepts (and agrees to be bound by all terms of) this License if You distribute only the self-extracting package (containing This Product) that does not allow the user to install (nor extract) the files contained in the package until he or she accepts and agrees to be bound by all terms and conditions of this License.
5. Without specific prior written permission from the authors of This Product (or from their common representative), You must not use the name of This Product, the names of the authors of This Product, or the names of the legal entities (or informal groups) of which the authors were/are members/employees, to endorse or promote Your Product or any work in which You include a modified or unmodified version of This Product, or to endorse or promote You or Your affiliates, or in a way that might suggest that Your Product (or any work in which You include a modified or unmodified version of This Product), You, or Your affiliates is/are endorsed by one or more authors of This Product, or in a way that might suggest that one or more authors of This Product is/are affiliated with You (or Your affiliates) or directly participated in the creation of Your Product or of any work in which You include a modified or unmodified version of This Product.
6. IF YOU ARE NOT SURE WHETHER YOU UNDERSTAND ALL PARTS OF THIS LICENSE OR IF YOU ARE NOT SURE WHETHER YOU CAN COMPLY WITH ALL TERMS AND CONDITIONS OF THIS LICENSE, YOU MUST NOT USE, COPY, MODIFY, CREATE DERIVATIVE WORKS OF, NOR (RE)DISTRIBUTE THIS PRODUCT, NOR ANY PORTION(S) OF IT. YOU SHOULD CONSULT WITH A LAWYER.
7. IF (IN RELEVANT CONTEXT) ANY PROVISION OF CHAPTER IV OF THIS LICENSE IS UNENFORCEABLE, INVALID, OR PROHIBITED UNDER APPLICABLE LAW IN YOUR JURISDICTION, YOU HAVE NO RIGHTS UNDER THIS LICENSE AND YOU MUST NOT USE, COPY, MODIFY, CREATE DERIVATIVE WORKS OF, NOR (RE)DISTRIBUTE THIS PRODUCT, NOR ANY PORTION(S) THEREOF.
8. Except as otherwise provided in this License, if any provision of this License, or a portion thereof, is found to be invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of this License, and such invalid or unenforceable provision shall be construed to reflect the original intent of the provision and shall be enforced to the maximum extent permitted by applicable law so as to effect the original intent of the provision as closely as possible.
____________________________________________________________
Third-Party Licenses
This Product contains components that were created by third parties and that are governed by third-party licenses, which are contained hereinafter (separated by lines consisting of underscores). Each of the third-party licenses applies only to (portions of) the source code file(s) in which the third-party license is contained or in which it is explicitly referenced, and to compiled or otherwise processed forms of such source code. None of the third-party licenses applies to This Product as a whole, even when it uses terms such as “product”, “program”, or any other equivalent terms/phrases. This Product as a whole is governed by the TrueCrypt License (see above). Some of the third-party components have been modified by the authors of This Product. Unless otherwise stated, such modifications and additions are governed by the TrueCrypt License (see above). Note: Unless otherwise stated, graphics and files that are not part of the source code are governed by the TrueCrypt License.
____________________________________________________________
License agreement for Encryption for the Masses.
Copyright (C) 1998-2000 Paul Le Roux. All Rights Reserved.
This product can be copied and distributed free of charge, including source code.
You may modify this product and source code, and distribute such modifications, and you may derive new works based on this product, provided that:
1. Any product which is simply derived from this product cannot be called E4M, or Encryption for the Masses.
2. If you use any of the source code in your product, and your product is distributed with source code, you must include this notice with those portions of this source code that you use.
Or,
If your product is distributed in binary form only, you must display on any packaging, and marketing materials which reference your product, a notice which states:
“This product uses components written by Paul Le Roux <pleroux@swprofessionals.com>”
3. If you use any of the source code originally by Eric Young, you must in addition follow his terms and conditions.
4. Nothing requires that you accept this License, as you have not signed it. However, nothing else grants you permission to modify or distribute the product or its derivative works.
These actions are prohibited by law if you do not accept this License.
5. If any of these license terms is found to be to broad in scope, and declared invalid by any court or legal process, you agree that all other terms shall not be so affected, and shall remain valid and enforceable.
6. THIS PROGRAM IS DISTRIBUTED FREE OF CHARGE, THEREFORE THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. UNLESS OTHERWISE STATED THE PROGRAM IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
7. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM, INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS, EVEN IF SUCH HOLDER OR OTHER PARTY HAD PREVIOUSLY BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
____________________________________________________________
Copyright (c) 1998-2008, Brian Gladman, Worcester, UK. All rights reserved.
LICENSE TERMS
The free distribution and use of this software is allowed (with or without changes) provided that:
DISCLAIMER
This software is provided ‘as is’ with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose.
____________________________________________________________
Copyright (C) 2002-2004 Mark Adler, all rights reserved
version 1.8, 9 Jan 2004
This software is provided ‘as-is’, without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
____________________________________________________________
We offer the product as is, and do not claim any rights to the name TrueCrypt or TrueCrypt.org – this is not a fork but the distribution of the product under Section II of the TrueCrypt license.
| Operating System | Signature | Download |
|---|---|---|
| Windows (XP/Vista/7/8) | sig | TrueCrypt Setup 7.1a.exe |
| MacOS X | sig | TrueCrypt 7.1a Mac OS X.dmg |
| Linux x86 / gui | sig | truecrypt-7.1a-linux-x86.tar.gz |
| Linux 64bit / gui | sig | truecrypt-7.1a-linux-x64.tar.gz |
| Linux x86 / headless | sig | truecrypt-7.1a-linux-console-x86.tar.gz |
| Linux 64bit / headless | sig | truecrypt-7.1a-linux-console-x64.tar.gz |
| Version | Signature | Download |
|---|---|---|
| 7.2 | sig | TrueCrypt 7.2 Source.zip |
| 7.2 | sig | TrueCrypt 7.2 Source.zip |
| 7.1a | sig | TrueCrypt 7.1a Source.zip |
| 7.1 | sig | TrueCrypt 7.1 Source.zip |
| 7.0a | sig | TrueCrypt 7.0a Source.zip |
| 7.0 | sig | TrueCrypt 7.0 Source.zip |
Rating
Want to support us?
You want to support us and help us covering costs? Also check out our partners!
Donate Bitcoin:
Bitcoin wallet: 16Qfd6KvyYozaJFrv61MLo5ajoidnhSRCG
Language packs contain third-party translations of the TrueCrypt user interface texts. Some language packs also contain translated TrueCrypt User Guide. Note that language packs are currently supported only by the Windows version of TrueCrypt.
To install a language pack, follow these steps:
To revert to English, select Settings -> Language. Then select English and click OK.
When a TrueCrypt volume is mounted, the operating system and third-party applications may write to unencrypted volumes (typically, to the unencrypted system volume) unencrypted information about the data stored in the TrueCrypt volume (e.g. filenames and locations of recently accessed files, databases created by file indexing tools, etc.), or the data itself in an unencrypted form (temporary files, etc.), or unencrypted information about the filesystem residing in the TrueCrypt volume. Note that Windows automatically records large amounts of potentially sensitive data, such as the names and locations of files you open, applications you run, etc.
In order to prevent data leaks, you must follow these steps (alternative steps may exist):