From Glitchdata
Jump to navigation Jump to search

Template:Use dmy dates Template:Infobox software

TrueCrypt is a discontinued source-available freeware utility used for on-the-fly encryption (OTFE). It can create a virtual encrypted disk within a file, or encrypt a partition or the whole storage device (pre-boot authentication).

On 28 May 2014, the TrueCrypt website announced that the project was no longer maintained and recommended users to find alternative solutions. Though development of TrueCrypt has ceased, an independent audit of TrueCrypt has concluded that no significant flaws are present.[1]

Alternatives include two freeware projects based on the TrueCrypt code, VeraCrypt and CipherShed, as well as numerous other commercial and open-source products.


Template:See also TrueCrypt was initially released as version 1.0 in February 2004, based on E4M (Encryption for the Masses). Several versions and many additional minor releases have been made since then, with the most current version being 7.2.[2]

E4M and SecurStar dispute

Original release of TrueCrypt was made by anonymous developers called "the TrueCrypt Team".[3] Shortly after version 1.0 was released in 2004, the TrueCrypt Team reported receiving email from Wilfried Hafner, manager of SecurStar, a computer security company.[4] According to the TrueCrypt Team, Hafner claimed in the email that the acknowledged author of E4M, developer Paul Le Roux, had stolen the source code from SecurStar as an employee.[4] It was further stated that Le Roux illegally distributed E4M, and authored an illegal license permitting anyone to base derivative work on the code and distribute it freely. Hafner alleges all versions of E4M always belonged only to SecurStar, and Le Roux did not have any right to release it under such a license.[4]

This led the TrueCrypt Team to immediately stop developing and distributing TrueCrypt, which they announced online through usenet.[4] TrueCrypt Team member David Tesařík stated that Le Roux informed the team that there was a legal dispute between himself and SecurStar, and that he received legal advisement not to comment on any issues of the case. Tesařík concluded that should the TrueCrypt Team continue distributing TrueCrypt, Le Roux may ultimately be held liable and be forced to pay consequent damages to SecurStar. To continue in good faith, he said, the team would need to verify the validity of the E4M license. However, because of Le Roux's need to remain silent on the matter, he was unable to confirm or deny its legitimacy, keeping TrueCrypt development in limbo.[4][5]

Thereafter, would-be visitors reported trouble accessing the TrueCrypt website, and 3rd party mirrors appeared online making the source code and installer continually available, outside of official sanction by the TrueCrypt Team.[6][7]

In the FAQ section of its website, SecurStar maintains its claims of ownership over both E4M and Scramdisk, another free encryption program. The company states that with those products, SecurStar "had a long tradition of open source software", but that "competitors had nothing better to do but to steal our source code", causing the company to make its products closed-source, forcing potential customers to place a substantial order and sign a non-disclosure agreement before being allowed to review the code for security.[8]

Le Roux himself has denied developing TrueCrypt in a court hearing in March 2016, in which he also confirmed he had written E4M.[9] On the other hand, he did reportedly order employees of his around 2007 to encrypt their hard drives with E4M, later with TrueCrypt.[10]

Version 2.0

Months later on 7 June 2004, TrueCrypt 2.0 was released.[2] The new version contained a different digital signature than that of the original TrueCrypt Team, with the developers now being referred to as "the TrueCrypt Foundation." The software license was also changed to the open source GNU General Public License (GPL). However, given the wide range of components with differing licenses making up the software, and the contested nature of the legality of the program's release, a few weeks later on 21 June, version 2.1 was released under the original E4M license to avoid potential problems relating to the GPL license.[2][11]

Version 2.1a of the software was released on 1 October 2004 on sub-domain.[2] By May 2005, the original TrueCrypt website returned and redirected visitors to

End of life announcement

On 28 May 2014, the TrueCrypt official website,, began redirecting visitors to with a HTTP 301 "Moved Permanently" status, which warned that the software may contain unfixed security issues, and that development of TrueCrypt was ended in May 2014, following Windows XP's end of support. The message noted that more recent versions of Windows have built-in support for disk encryption using BitLocker, and that Linux and OS X had similar built-in solutions, which the message states renders TrueCrypt unnecessary. The page recommends any data encrypted by TrueCrypt be migrated to other encryption setups and offered instructions on moving to BitLocker. The SourceForge project page for the software at was updated to display the same initial message, and the status was changed to "inactive."[12] The page also announced a new software version, 7.2, which only allows decryption.

Initially, the authenticity of the announcement and new software was questioned.[13][14][15] Multiple theories attempting to explain the reason behind the announcement arose throughout the tech community.[16][17][18]

Shortly after the final release announcement titled "Yes... TrueCrypt is still safe to use", Gibson Research Corporation posted a Final Release Repository to host the last official Read/Write capable version of Truecrypt, from which the option to create new containers was removed. They also posted an article addressing the security concerns of current users and documenting community efforts to continue the project.[18]


Template:Primary TrueCrypt may still be used on supported platforms.[19] There are at least three TrueCrypt forks, as well as open-source and commercial alternatives.


Template:Further information As of June 2014, there is also a software fork named CipherShed, with resources and infrastructure funded[20] by,[21][22] developed by, and audited by a crowdfunded security audit team (c.f. Template:Section link).[23]


Template:Further information VeraCrypt is a fork of TrueCrypt. Security improvements have been implemented and issues raised by the TrueCrypt code audit just before the TrueCrypt developers retired have been addressed.


tc-play is an independently-developed open-source implementation of the TrueCrypt format.[24] It is a free command-line implementation available for Linux and DragonFly BSD under BSD license.[25][26] Its disk encryption method and container format are managed by Linux Kernel via dm-crypt module.[27][28] ZuluCrypt, a graphical front end for tc-play,[29] is available on several Linux distributions.[30]

Operating systems

TrueCrypt supports Windows, OS X and Linux operating systems.[31] Both 32-bit and 64-bit versions of these operating systems are supported, except for Windows IA-64 (not supported) and Mac OS X 10.6 Snow Leopard (runs as a 32-bit process).[31] The version for Windows 7, Windows Vista, and Windows XP can encrypt the boot partition or entire boot drive.[32]

Independent implementations

There is an independent, compatible[25][26] implementation, tcplay, for DragonFly BSD[25] and Linux.[26][33]

The Dm-crypt module included in default Linux kernel supports a TrueCrypt target called "tcw" since Linux version 3.13.[28][34][35]

Encryption scheme


Individual ciphers supported by TrueCrypt are AES, Serpent, and Twofish. Additionally, five different combinations of cascaded algorithms are available: AES-Twofish, AES-Twofish-Serpent, Serpent-AES, Serpent-Twofish-AES and Twofish-Serpent.[36] The cryptographic hash functions available for use in TrueCrypt are RIPEMD-160, SHA-512, and Whirlpool.[37]

Modes of operation

TrueCrypt currently uses the XTS mode of operation.[38] Prior to this, TrueCrypt used LRW mode in versions 4.1 through 4.3a, and CBC mode in versions 4.0 and earlier.[2] XTS mode is thought to be more secure than LRW mode, which in turn is more secure than CBC mode.[39]

Although new volumes can only be created in XTS mode, TrueCrypt is backward compatible with older volumes using LRW mode and CBC mode.[2] Later versions produce a security warning when mounting CBC mode volumes and recommend that they be replaced with new volumes in XTS mode.


The header key and the secondary header key (XTS mode) are generated using PBKDF2 with a 512-bit salt and 1000 or 2000 iterations, depending on the underlying hash function used.[40]

Plausible deniability

TrueCrypt supports a concept called plausible deniability,[41] by allowing a single "hidden volume" to be created within another volume.[42] In addition, the Windows versions of TrueCrypt have the ability to create and run a hidden encrypted operating system whose existence may be denied.[43]

The TrueCrypt documentation lists many ways in which TrueCrypt's hidden volume deniability features may be compromised (e.g. by third party software which may leak information through temporary files, thumbnails, etc., to unencrypted disks) and possible ways to avoid this.[44] In a paper published in 2008 and focused on the then latest version (v5.1a) and its plausible deniability, a team of security researchers led by Bruce Schneier states that Windows Vista, Microsoft Word, Google Desktop, and others store information on unencrypted disks, which might compromise TrueCrypt's plausible deniability. The study suggested the addition of a hidden operating system functionality; this feature was added in TrueCrypt 6.0. When a hidden operating system is running, TrueCrypt also makes local unencrypted filesystems and non-hidden TrueCrypt volumes read-only to prevent data leaks.[43] The security of TrueCrypt's implementation of this feature was not evaluated because the first version of TrueCrypt with this option had only recently been released.[45]

There was a functional evaluation of the deniability of hidden volumes in an earlier version of TrueCrypt by Schneier et al. that found security leaks.[46]

Identifying TrueCrypt volumes

When analyzed, TrueCrypt volumes appear to have no header and contain random data.[47] TrueCrypt volumes have sizes that are multiples of 512 due to the block size of the cipher mode[38] and key data is either 512 bytes stored separately in the case of system encryption or two 128kB headers for non-system containers.[48] Forensics tools may use these properties of file size, apparent lack of a header, and randomness tests to attempt to identify TrueCrypt volumes.[49] Although these features give reason to suspect a file to be a TrueCrypt volume, there are, however, some programs which exist for the purpose of securely erasing files by employing a method of overwriting file contents, and free disk space, with purely random data (i.e. "shred" & "scrub"[50]), thereby creating reasonable doubt to counter pointed accusations declaring a file, made of statistically random data, to be a TrueCrypt file.[41][51]

If a system drive, or a partition on it, has been encrypted with TrueCrypt, then only the data on that partition is deniable. When the TrueCrypt boot loader replaces the normal boot loader, an offline analysis of the drive can positively determine that a TrueCrypt boot loader is present and so lead to the logical inference that a TrueCrypt partition is also present. Even though there are features to obfuscate its purpose (i.e. displaying a BIOS-like message to misdirect an observer such as, "Non-system disk" or "disk error"), these reduce the functionality of the TrueCrypt boot loader and do not hide the content of the TrueCrypt boot loader from offline analysis.[52] Here again, the use of a hidden operating system is the suggested method for retaining deniability.[43]


TrueCrypt supports parallelized[53]Template:Rp encryption for multi-core systems and, under Microsoft Windows, pipelined read/write operations (a form of asynchronous processing)[53]Template:Rp to reduce the performance hit of encryption and decryption. On newer processors supporting the AES-NI instruction set, TrueCrypt supports hardware-accelerated AES to further improve performance.[53]Template:Rp The performance impact of disk encryption is especially noticeable on operations which would normally use Direct Memory Access (DMA), as all data must pass through the CPU for decryption, rather than being copied directly from disk to RAM.

In a test carried out by Tom's Hardware, although TrueCrypt is slower compared to an unencrypted disk, the overhead of real-time encryption was found to be similar regardless of whether mid-range or state-of-the-art hardware is in use, and this impact was "quite acceptable".[54] In another article the performance cost was found to be unnoticeable when working with "popular desktop applications in a reasonable manner", but it was noted that "power users will complain".[55]

Incompatibility with FlexNet Publisher and SafeCast

Template:Main article Installing third-party software which uses FlexNet Publisher or SafeCast (which are used for preventing software piracy on products by Adobe such as Adobe Photoshop) can damage the TrueCrypt bootloader on Windows partitions/drives encrypted by TrueCrypt and render the drive unbootable.[56] This is caused by the inappropriate design of FlexNet Publisher writing to the first drive track and overwriting whatever non-Windows bootloader exists there.[57]

Security concerns

TrueCrypt is vulnerable to various known attacks which are also present in other software-based disk encryption software such as BitLocker. To prevent those, the documentation distributed with TrueCrypt requires users to follow various security precautions.[58] Some of those attacks are detailed below.

Encryption keys stored in memory

TrueCrypt stores its keys in RAM; on an ordinary personal computer the DRAM will maintain its contents for several seconds after power is cut (or longer if the temperature is lowered). Even if there is some degradation in the memory contents, various algorithms can intelligently recover the keys. This method, known as a cold boot attack (which would apply in particular to a notebook computer obtained while in power-on, suspended, or screen-locked mode), has been successfully used to attack a file system protected by TrueCrypt.[59]

Physical security

TrueCrypt documentation states that TrueCrypt is unable to secure data on a computer if an attacker physically accessed it and TrueCrypt is used on the compromised computer by the user again (this does not apply to a common case of a stolen, lost, or confiscated computer).[60] The attacker having physical access to a computer can, for example, install a hardware/software keylogger, a bus-mastering device capturing memory, or install any other malicious hardware or software, allowing the attacker to capture unencrypted data (including encryption keys and passwords), or to decrypt encrypted data using captured passwords or encryption keys. Therefore, physical security is a basic premise of a secure system. Attacks such as this are often called "evil maid attacks".[61]


TrueCrypt documentation states that TrueCrypt cannot secure data on a computer if it has any kind of malware installed. Malware may log keystrokes, thus exposing passwords to an attacker.[62]

The "Stoned" bootkit

The "Stoned" bootkit, an MBR rootkit presented by Austrian software developer Peter Kleissner at the Black Hat Technical Security Conference USA 2009,[63][64] has been shown capable of tampering TrueCrypt's MBR, effectively bypassing TrueCrypt's full volume encryption.[65][66][67][68][69] Potentially every hard disk encryption software is affected by this kind of attack if the encryption software does not rely on hardware-based encryption technologies like TPM, or if the attack is made with administrative privileges while the encrypted operating system is running.[70][71]

Two types of attack scenarios exist in which it is possible to maliciously take advantage of this bootkit: in the first one, the user is required to launch the bootkit with administrative privileges once the PC has already booted into Windows; in the second one, analogously to hardware keyloggers, a malicious person needs physical access to the user's TrueCrypt-encrypted hard disk: in this context this is needed to modify the user's TrueCrypt MBR with that of the Stoned bootkit and then place the hard disk back on the unknowing user's PC, so that when the user boots the PC and types his/her TrueCrypt password on boot, the "Stoned" bootkit intercepts it thereafter because, from that moment on, the Stoned bootkit is loaded before TrueCrypt's MBR in the boot sequence. The first type of attack can be prevented as usual by good security practices, e.g. avoid running non-trusted executables with administrative privileges. The second one can be successfully neutralized by the user if he/she suspects that the encrypted hard disk might have been physically available to someone he/she does not trust, by booting the encrypted operating system with TrueCrypt's Rescue Disk instead of booting it directly from the hard disk. With the rescue disk, the user can restore TrueCrypt's MBR to the hard disk.[72]

Trusted Platform Module

The FAQ section of the TrueCrypt website states that the Trusted Platform Module (TPM) cannot be relied upon for security, because if the attacker has physical or administrative access to the computer and you use it afterwards, the computer could have been modified by the attacker e.g. a malicious component—such as a hardware keystroke logger—could have been used to capture the password or other sensitive information. Since the TPM does not prevent an attacker from maliciously modifying the computer, TrueCrypt will not support the TPM.[71]

Security audits

In 2013 a graduate student at Concordia University published a detailed online report, in which he states that he has confirmed the integrity of the distributed Windows binaries of version 7.1a.[73]

A crowdfunding campaign attempting to conduct an independent security audit of TrueCrypt was successfully funded in October 2013. A non-profit organization called the Open Crypto Audit Project (OCAP) was formed, calling itself "a community-driven global initiative which grew out of the first comprehensive public audit and cryptanalysis of the widely used encryption software TrueCrypt".[74] The organization established contact with TrueCrypt developers, who welcomed the audit.[75][76] Phase I of the audit was successfully completed on 14 April 2014, finding "no evidence of backdoors or malicious code". Matthew D. Green, one of the auditors, added "I think it's good that we didn't find anything super critical."[77]

One day after TrueCrypt's end of life announcement, OCAP confirmed that the audit would continue as planned, with Phase II expected to begin in June 2014 and wrap up by the end of September.[78][79] The Phase II audit was delayed, but was completed 2 April 2015 by NCC Cryptography Services. This audit "found no evidence of deliberate backdoors, or any severe design flaws that will make the software insecure in most instances."[80][81][82] The French National Agency for the Security of Information Systems (ANSSI) stated that while TrueCrypt 6.0 and 7.1a have previously attained ANSSI certification, migration to an alternate certified product is recommended as a precautionary measure.[83]

According to Gibson Research Corporation, Steven Barnhart wrote to an email address for a TrueCrypt Foundation member he had used in the past and received several replies from "David". According to Barnhart, the main points of the email messages were that the TrueCrypt Foundation was "happy with the audit, it didn't spark anything", and that the reason for the announcement was that "there is no longer interest [in maintaining the project]."[84]

According to a study released 29 September 2015, TrueCrypt includes two vulnerabilities in the driver that TrueCrypt installs on Windows systems allowing an attacker arbitrary code execution and privilege escalation via DLL hijacking.[85] In January 2016, the vulnerability was fixed in VeraCrypt,[86] but it remains unpatched in TrueCrypt's unmaintained installers.

Legal cases

Operation Satyagraha

In July 2008, several TrueCrypt-secured hard drives were seized from Brazilian banker Daniel Dantas, who was suspected of financial crimes. The Brazilian National Institute of Criminology (INC) tried unsuccessfully for five months to obtain access to his files on the TrueCrypt-protected disks. They enlisted the help of the FBI, who used dictionary attacks against Dantas' disks for over 12 months, but were still unable to decrypt them.[87][88]

United States v. John Doe

In 2012 the United States 11th Circuit Court of Appeals ruled that a John Doe TrueCrypt user could not be compelled to decrypt several of his hard drives.[89][90][91] The court's ruling noted that FBI forensic examiners were unable to get past TrueCrypt's encryption (and therefore were unable to access the data) unless Doe either decrypted the drives or gave the FBI the password, and the court then ruled that Doe's Fifth Amendment right to remain silent legally prevented the Government from making him or her do so.[92][93]

David Miranda

Template:Further information On 18 August 2013 David Miranda, partner of journalist Glenn Greenwald, was detained at London's Heathrow Airport by Metropolitan Police while en route to Rio de Janeiro from Berlin. He was carrying with him an external hard drive said to be containing sensitive documents pertaining to the 2013 global surveillance disclosures sparked by Edward Snowden. Contents of the drive were encrypted by TrueCrypt, which authorities said "renders the material extremely difficult to access."[94] Detective Superintendent Caroline Goode stated the hard drive contained around 60 gigabytes of data, "of which only 20 have been accessed to date." She further stated the process to decode the material was complex and "so far only 75 documents have been reconstructed since the property was initially received."[94]

Guardian contributor Naomi Colvin concluded the statements were misleading, stating that it was possible Goode was not even referring to any actual encrypted material, but rather deleted files reconstructed from unencrypted, unallocated space on the hard drive, or even plaintext documents from Miranda's personal effects.[95] Glenn Greenwald supported this assessment in an interview with Democracy Now!, mentioning that the UK government filed an affidavit asking the court to allow them to retain possession of Miranda's belongings. The grounds for the request were that they could not break the encryption, and were only able to access 75 of the documents that he was carrying, which Greenwald said "most of which were probably ones related to his school work and personal use."[96]

James DeSilva

In February 2014, an Arizona Department of Real Estate IT department employee, James DeSilva, was arrested on charges of sexual exploitation of a minor through the sharing of explicit images over the Internet. His computer, encrypted with TrueCrypt, was seized, and DeSilva refused to reveal the password. Forensics detectives from the Maricopa County Sheriff's Office were unable to gain access to his stored files.[97]

Lauri Love

In October 2013, British–Finnish activist Lauri Love was arrested by the National Crime Agency (NCA) on charges of hacking into a US department or agency computer and one count of conspiring to do the same.[98][99][100] The government confiscated all of his electronics and demanded he provide them with the necessary keys to decrypt the devices. Love refused. On 10 May 2016 a District Judge (Magistrate's Court) rejected a request by the NCA that Love be forced to turn over his encryption keys or passwords to TrueCrypt files on an SD card and hard drives that were among the confiscated property.[101]

License and source model

TrueCrypt was released under the "TrueCrypt License" which is unique to the TrueCrypt software.[102][103] It is not part of the pantheon of widely used open source licenses and is not a free software license according to the Free Software Foundation (FSF) license list, as it contains distribution and copyright-liability restrictions.[104] As of version 7.1a (the last full version of the software, released Feb 2012), the TrueCrypt License was Version 3.0.

Discussion of the licensing terms on the Open Source Initiative (OSI)'s license-discuss mailing list in October 2013 suggests that the TrueCrypt License has made progress towards compliance with the Open Source Definition but would not yet pass if proposed for certification as Open Source software.[104][105]

According to current OSI president Simon Phipps: is not at all appropriate for [TrueCrypt] to describe itself as "open source." This use of the term "open source" to describe something under a license that's not only unapproved by OSI but known to be subject to issues is unacceptable.[104]

As a result of its questionable status with regard to copyright restrictions and other potential legal issues,[106] the TrueCrypt License is not considered "free" by several major Linux distributions and is therefore not included in Debian,[107] Ubuntu,[108] Fedora,[109] or openSUSE.[110]

The wording of the license raises doubts whether those who use it have the right to modify it and use it within other projects. Cryptographer Matthew Green noted that "There are a lot of things [the developers] could have done to make it easier for people to take over this code, including fixing the licensing situation", and speculates that since they didn't do those things (including making the license more friendly), their intent was to prevent anyone from building on their code in the future.[111]

End of life and license version 3.1

28 May 2014 announcement of discontinuation of TrueCrypt also came with a new version 7.2 of the software. Among the many changes to the source code from the previous release were changes to the TrueCrypt License — including removal of specific language that required attribution of TrueCrypt as well as a link to the official website to be included on any derivative products — forming a license version 3.1.[112]

On 16 June 2014, the only alleged TrueCrypt developer still answering email replied to a message by Matthew Green with regards to the licensing situation. He is not willing to change the license to an open source one, believes that Truecrypt should not be forked, and that if someone wants to create a new version they should start from scratch.[113][114]


The TrueCrypt trademark was registered in the Czech Republic under name of David Tesařík.[115]

In the US, the TrueCrypt trademark also was registered under name of David Tesařík[116] as well as the trademark of the logo.[117]

The company TrueCrypt was registered in the US by a person named Ondrej Tesarik.[118] This non-profit organization was functional as far as it has filed tax returns.[119]

Planned features

Before the end of life notice, the TrueCrypt website[120] stated that the following features were planned for future releases:

  • Full support for Windows 8
  • Ability to encrypt Windows system partitions/drives on UEFI-based computers
  • Command line options for volume creation (already implemented in Linux and Mac OS X versions)
  • "Raw" CD/DVD volumes





External links


Template:Cryptography navbox Template:Cryptographic software

  1. "Open Crypto Audit Project".
  2. 2.0 2.1 2.2 2.3 2.4 2.5 "Version History". TrueCrypt Foundation. Retrieved 1 October 2009.
  3. "Version Information". TrueCrypt User’s Guide, version 1.0. TrueCrypt Team. 2 February 2004. Archived from the original on 5 February 2004. Retrieved 28 May 2014.
  4. 4.0 4.1 4.2 4.3 4.4 Template:Cite newsgroup
  5. Template:Cite newsgroup
  6. Template:Cite newsgroup
  7. Template:Cite newsgroup
  8. "Is the source code of your software available?". Drivecrypt FAQ. SecurStar. Archived from the original on 2 June 2014. Retrieved 28 May 2014.
  9. Ratliff, Evan (29 April 2016). "The Next Big Deal".
  10. Ratliff, Evan. "I’m Your Boss Now".
  11. "Version History". TrueCrypt User’s Guide, version 3.1a. TrueCrypt Foundation. 7 February 2005. Archived from the original on 30 December 2008. Retrieved 2 March 2017.
  12. tc-foundation (28 May 2014). "TrueCrypt project page". SourceForge. Archived from the original on 30 May 2014. Retrieved 30 May 2014.
  13. Template:Citation
  14. O'Neill, Patrick (28 May 2014). "TrueCrypt, encryption tool used by Snowden, shuts down due to alleged 'security issues'". The Daily Dot. Retrieved 28 May 2014.
  15. Template:Citation
  16. Template:Citation
  17. Template:Citation
  18. 18.0 18.1 Template:Citation
  19. Template:Citation
  20. Template:Citation
  21. Template:Citation
  22. Template:Citation
  23. Template:Citation
  24. [citation needed]
  25. 25.0 25.1 25.2 Cite error: Invalid <ref> tag; no text was provided for refs named dragonfly
  26. 26.0 26.1 26.2 "README". tc-play. Retrieved 14 March 2014.
  27. "dm-crypt: Linux kernel device-mapper crypto target - IV generators". cryptsetup. 11 January 2014. Retrieved 13 June 2014.
  28. 28.0 28.1 "index : kernel/git/stable/linux-stable.git - path: root/drivers/md/dm-crypt.c". cgit. 20 January 2014. Line 241. Retrieved 13 June 2014.
  29. [citation needed]
  30. [citation needed]
  31. 31.0 31.1 "Supported Operating Systems". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  32. "Operating Systems Supported for System Encryption". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  33. "Fedora Review Request: tcplay - Utility to create/open/map TrueCrypt-compatible volumes". FEDORA. Retrieved 25 January 2012.
  34. "dm-crypt: Linux kernel device-mapper crypto target - IV generators". cryptsetup. 11 January 2014. Retrieved 10 June 2014.
  35. "[dm-devel [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers."]. Retrieved 17 June 2014.
  36. "Encryption Algorithms". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  37. "Hash Algorithms". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  38. 38.0 38.1 "Modes of Operation". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  39. Fruhwirth, Clemens (18 July 2005). "New Methods in Hard Disk Encryption" (PDF). Institute for Computer Languages, Theory and Logic Group, Vienna University of Technology. Retrieved 10 March 2007.
  40. "Header Key Derivation, Salt, and Iteration Count". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  41. 41.0 41.1 "Plausible Deniability". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  42. "Hidden Volume". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  43. 43.0 43.1 43.2 "Hidden Operating System". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  44. "Security Requirements for Hidden Volumes". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  45. Template:Cite conference
  46. Schneier, UW Team Show Flaw In TrueCrypt Deniability. Accessed on: 12 June 2012
  47. Piccinelli, Mario, and Paolo Gubian. "Detecting Hidden Encrypted Volume Files via Statistical Analysis." International Journal of Cyber-Security and Digital Forensics (IJCSDF) 3.1 (2014): 30-37.
  48. "TrueCrypt Volume Format Specification". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  49. "Archive". Archived from the original on 24 May 2014. Retrieved 2 March 2017.
  50. "diskscrub - disk overwrite utility - Google Project Hosting". Retrieved 16 July 2014.
  51. "Plausible Deniability". FreeOTFE. Archived from the original on 24 January 2013.
  52. TrueCrypt FAQ - see question I use pre-boot authentication. Can I prevent a person (adversary) that is watching me start my computer from knowing that I use TrueCrypt?
  53. 53.0 53.1 53.2 "TrueCrypt User Guide". TrueCrypt Foundation. 7 February 2012.
  54. Schmid, Patrick; Roos, Achim (28 April 2010). "Conclusion". System Encryption: BitLocker And TrueCrypt Compared. Tom's Hardware.,2587-9.html. Retrieved 24 May 2014.
  55. Schmid, Patrick; Roos, Achim (28 April 2010). "Conclusion". Protect Your Data With Encryption. Tom's Hardware.,2125-11.html. Retrieved 24 May 2014.
  56. "Freeze when you reboot a Windows system that has TrueCrypt Disk Encryption software and Adobe applications installed". Adobe Creative Suite Help. Adobe Systems. 16 November 2009. Retrieved 24 May 2014.
  57. "Incompatibilities". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  58. "Security Requirements and Precautions". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  59. Alex Halderman. "Lest We Remember: Cold Boot Attacks on Encryption Keys".
  60. "Physical Security". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  61. Schneier, Bruce (23 October 2009). ""Evil Maid" Attacks on Encrypted Hard Drives". Schneier on Security. Retrieved 24 May 2014.
  62. "Malware". TrueCrypt Documentation. TrueCrypt Foundation. Retrieved 24 May 2014.
  63. "Stoned bootkit White Paper" (PDF). Black Hat Technical Security Conference USA 2009. Peter Kleissner. Retrieved 5 August 2009.
  64. "Stoned bootkit Presentation Slides" (PDF). Black Hat Technical Security Conference USA 2009. Peter Kleissner. Retrieved 5 August 2009.
  65. "Bootkit bypasses hard disk encryption". The H-Security ( Heise Media UK Ltd.. Archived from the original on 1 August 2009. Retrieved 5 August 2009.
  66. David M Williams (7 September 2009). "The dark side of open source software is Stoned". iTWire.
  67. Hunt, Simon (4 August 2009). "TrueCrypt vs Peter Kleissner, Or Stoned BootKit Revisited..". Simon Hunt. Retrieved 24 May 2014.
  68. Uli Ries (30 July 2009). "Bootkit hebelt Festplattenverschlüsselung aus" (in German). Heise Online.
  69. "Windows-Hacking: TrueCrypt Verschlüsselung umgangen" (in German). Gulli News. 30 July 2009.
  70. "Stoned bootkit attacking TrueCrypt's full volume encryption". TrueCrypt Foundation mail in response to Peter Kleissner on 18 July 2009. Retrieved 5 August 2009.
  71. 71.0 71.1 "Some encryption programs use TPM to prevent attacks. Will TrueCrypt use it too?". TrueCrypt FAQ. TrueCrypt Foundation. Retrieved 24 August 2011.
  72. Kleissner, Peter (21 July 2009). "TrueCrypt Foundation is a joke to the security industry, pro Microsoft". Peter Kleissner. Archived from the original on 18 August 2010. Retrieved 5 August 2009.
  73. Xavier de Carné de Carnavalet (2013). "How I compiled TrueCrypt 7.1a for Win32 and matched the official binaries".
  74. "Welcome to the Open Crypto Audit Project". Open Crypto Audit Project. Archived from the original on 31 May 2014. Retrieved 31 May 2014.
  75. "The TrueCrypt Audit Project". Indiegogo. Retrieved 2 November 2013.
  76. "TrueCrypt Audit Endorsed by Development Team". Threatpost. Retrieved 2 November 2013.
  77. Template:Citation
  78. Template:Citation
  79. Template:Citation
  80. Green, Matthew (2 April 2015). "Truecrypt report". A Few Thoughts on Cryptographic Engineering. Retrieved 4 April 2015.
  81. Green, Matthew (18 February 2015). "Another update on the Truecrypt audit". A Few Thoughts on Cryptographic Engineering. Retrieved 22 February 2015.
  82. "Truecrypt Phase Two Audit Announced". Cryptography Services. NCC Group. 18 February 2015. Retrieved 22 February 2015.
  83. "Possible abandon de TrueCrypt par ses développeurs". Agence nationale de la sécurité des systèmes d’information. 2 June 2014. Retrieved 21 June 2014.
  84. Gibson, Steve (30 May 2014). "And then the TrueCrypt developers were heard from!". TrueCrypt Latest Release Repository. Gibson Research Corporation. Archived from the original on 30 May 2014. Retrieved 30 May 2014.
  86. CVE-2016-1281: TrueCrypt and VeraCrypt Windows installers allow arbitrary code execution with elevation of privilege
  87. Leyden, John (28 June 2010). "Brazilian banker's crypto baffles FBI". The Register. Retrieved 13 August 2010.
  88. Template:Citation
  89. Template:Citation
  90. Template:Citation
  91. "Court Rules TrueCrypt User Cannot Be Compelled To Decrypt Hard Disk". Retrieved 16 July 2014.
  92. Template:Cite court
  93. United States v. John Doe
  94. 94.0 94.1 Template:Citation
  95. Colvin, Naomi (31 August 2013). "#Miranda: Where is the UK Government getting its numbers from?". Extraordinary Popular Delusions. Archived from the original on 30 May 2014. Retrieved 30 May 2014.
  96. Template:Cite AV media
  97. Template:Citation
  98. Halliday, Josh (29 October 2013). "Briton Lauri Love faces hacking charges in US". Guardian Media Group. Retrieved 13 May 2016.
  99. "Briton Lauri Love faces new US hacking charges". BBC News Online. BBC. 27 February 2014. Retrieved 13 May 2016.
  100. "Hacker Charged with Breaching Multiple Government Computers and Stealing Thousands of Employee and Financial Records". Alexandria, VA: U.S. Department of Justice. 24 July 2014. Retrieved 15 May 2016.
  101. Masnick, Mike (10 May 2016). "Judge Rejects Attempt To Force Lauri Love To Decrypt His Computers, Despite Never Charging Him With A Crime". Floor64.
  102. TrueCrypt License. Accessed on: 21 May 2012 Template:Dead link
  103. TrueCrypt Collective License. Accessed on: 4 June 2014
  104. 104.0 104.1 104.2 Template:Citation
  105. Fontana, Richard (October 2013). "TrueCrypt license (not OSI-approved; seeking history, context).". Archived from the original on 29 October 2013. Retrieved 26 October 2013.
  106. Tom Callaway of Red Hat about TrueCrypt licensing concern Accessed on 10 July 2009
  107. Debian Bug report logs - #364034. Accessed on: 12 January 2009.
  108. Bug #109701 in Ubuntu. Accessed on: 20 April 2009
  109. TrueCrypt licensing concern Accessed on: 20 April 2009
  110. non-OSI compliant packages in the openSUSE Build Service. Accessed on: 20 April 2009
  111. "TrueCrypt Goes the Way of Lavabit as Developers Shut it Down Without Warning". Retrieved 1 June 2014.
  112. "TrueCrypt License Version 3.1". TrueCrypt Foundation. 28 May 2014. Retrieved 29 May 2014.
  113. Green, Matthew D. (16 June 2014). "Here is the note..." (Twitter). Archived from the original on 22 June 2014. Retrieved 22 June 2014.
  114. Template:Citation
  115. Intellectual Property Digital Library; search trademarks directory for IRN/925625
  116. "Trademark Electronic Search System (TESS)". Retrieved 16 July 2014. (search trademark directory for "TrueCrypt")
  117. "77165797 - Markeninformation USPTO - via tmdb".,77165797.html. Retrieved 16 July 2014.
  118. "Entity Details - Secretary of State, Nevada". 19 August 2009. Retrieved 16 July 2014.
  119. "Truecrypt Foundation". Retrieved 16 July 2014.
  120. "Future". TrueCrypt Foundation. Archived from the original on 4 June 2014. Retrieved 24 May 2014. Template:Dead link