- Truecrypt org update#
- Truecrypt org software#
- Truecrypt org code#
- Truecrypt org license#
- Truecrypt org windows#
I realize this is a great deal to ask, but I would ask you to consider the alternative.
Truecrypt org software#
If that’s not possible, we would accept a clear statement that you would prefer the software not be renamed. We would also like permission to use the Truecrypt trademark as part of this effort.
Truecrypt org license#
What we would like is permission to take at least portions of the current codebase and fork it under a standard open source license (e.g., GPL/MIT/BSD). Of course some will fork the reject regardless of the legal issues, but this doesn’t seem appropriate without clear guidance. The main concern we have right now is with the license structure and trademarks associated with Truecrypt. The current plan is being led by a group of people who have a great deal of experience with cryptography and the expertise to identify flaws, but would prefer not to engineer from scratch. Even though this will require some substantial re-development it still seems more practical than starting from scratch.
Truecrypt org code#
That means fully auditing all of the crypto/container and bootloader code and (likely) replacing much of it with fresh implementations. We’d like the project to continue, but in a responsible way. In fact, it may become significantly less secure if it goes forward as samizdat or as part of some unauthorized fork. Moreover, Truecrypt is unlikely to ‘go away’ just because the developers have abandoned the project. We think Truecrypt is an important project - no proprietary disk encryption system offers cross-platform support and the same feature set. I think this interest has reached the point where a fork is virtually inevitable. Now that you’re no longer maintaining it, there seems to be a great deal of interest in forking it. I understand and can sympathize with that.įor the past several months we’ve been (very slowly) auditing the TC code. I understand from seeing some previous emails that you were one of the Truecrypt developers, and that you’re no longer interested in continuing work on the project. He had prior contact with the TrueCrypt developers and reached out to them about forking its development with this email: If you read our piece, The Mystery Of TrueCrypt's Disappearance, you would know that one of the principals of the effort to audit TrueCrypt was Matthew Green ( a Cryptography Research Professor at the Johns Hopkins University). TrueCrypt Developer Says Open Source Fork Is "Impossible" The Mystery Of TrueCrypt's Disappearance If you like this article, please share it! -> Even worse - they are now denying the world the right to "fork" TrueCrypt's development. Well, it's been more than 3 weeks since TrueCrypt went down, and one thing's for sure - the website was not hacked, and it was the actual intent of the mysterious developers of TrueCrypt to pull the plug. On the other hand, there were conspiracy theories that the developers were being threatened by the NSA to divulge or add a backdoor, or were the NSA themselves! On one end, many TrueCrypt users were hoping that the website was just hacked and that the world, as they knew it, would return. There has been much speculation about the reasons for pulling the plug. However, this version of TrueCrypt will only decrypt TrueCrypt containers - its encryption ability has been disabled / removed.
Truecrypt org update#
Right at the end is a link to TrueCrypt 7.2, the first update since TrueCrypt 7.1a was released in 2012. That warning is then followed by instructions on how users may migrate from TrueCrypt to BitLocker. You should migrate any data encrypted by TrueCrypt to encrypted disks or virtual disk images supported on your platform. Such integrated support is also available on other platforms (click here for more information).
Truecrypt org windows#
Windows 8/7/Vista and later offer integrated support for encrypted disks and virtual disk images. The development of TrueCrypt was ended in 5/2014 after Microsoft terminated support of Windows XP. This page exists only to help migrate existing data encrypted by TrueCrypt. WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues They shut down the website and redirected visitors to a simple page hosted by SourceForge, with a disturbing warning : Sometime on the 28th of May, 2014, the anonymous developers of TrueCrypt mysteriously pulled the plug on their popular encryption software. ED#176 : TrueCrypt Developer Drops New Bombshell - Open Source Fork "Impossible"