Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
TrueCrypt
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===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.<ref name="truecrypt-archive">{{cite web|url=https://github.com/DrWhax/truecrypt-archive/blob/master/doc/License-v3.1.txt|title=truecrypt-archive/License-v3.1.txt at master Β· DrWhax/truecrypt-archive|website=GitHub|date=28 Mar 2014|access-date=23 Jul 2018}}</ref> Cryptographer Matthew Green, who had help raise funds for TrueCrypt's audit noted a connection between TrueCrypt's refusal to change the license and their departure-time warning. "They set the whole thing on fire, and now maybe nobody is going to trust it because they'll think there's some big evil vulnerability in the code."<ref>{{cite web|url=http://www.ibtimes.co.uk/truecrypt-goes-way-lavabit-developers-shut-it-down-without-warning-1450467 |title=TrueCrypt Goes the Way of Lavabit as Developers Shut it Down Without Warning |date=29 May 2014 |publisher=Ibtimes.co.uk |access-date=1 June 2014}}</ref> On 16 June 2014, the only alleged TrueCrypt developer still answering email replied to a message by Matthew Green asking for permission to use the TrueCrypt trademark for a fork released under a standard open source license. Permission was denied, which led to the two known forks being named [[VeraCrypt]] and CipherShed as well as a re-implementation named tc-play rather than TrueCrypt.<ref>{{cite web |last=Green |first=Matthew D. |author-link=Matthew D. Green |title=Here is the note... |date=16 June 2014 |url=https://twitter.com/matthew_d_green/status/478721271316758528 |format=Twitter |access-date=22 June 2014 |archive-url=https://web.archive.org/web/20140817063344/https://twitter.com/matthew_d_green/status/478721271316758528 |archive-date=17 August 2014 |url-status=dead |df=dmy }}</ref><ref>{{Citation | last =Goodin | first =Dan | title =Following TrueCrypt's bombshell advisory, developer says fork is "impossible" | work=[[Ars Technica]] |publisher=[[CondΓ© Nast]] | date =19 June 2014 | url =https://arstechnica.com/security/2014/06/following-truecrypts-bombshell-advisory-developer-says-fork-is-impossible/ | access-date = 22 June 2014}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)