/syglug/truecrypt: Another TrueCrypt v7.1 archive, though apparently not the latest./DrWhax/truecrypt-archive: This is a frequently cited, nearly complete, historical repository of previous TrueCrypt versions, tracking its evolution all the way back to when it was previously named “ScramDisk” (which is when we were first using and working with it).what TrueCrypt becomes will not be called “TrueCrypt.” Given the deliberate continuing licensing encumbrance of the registered TrueCrypt trademark, it seems more likely that the current TrueCrypt code will be forked and subsequently renamed.
TrueCrypt.ch: A just launched, Swiss-based, possible new home for TrueCrypt.
#MAC TRUECRYPT ALTERNATIVE ARCHIVE#
Quoting TrueCrypt Developer David: “There is no longer interest.”Īlso this thread of tweets seemed to indicate that a formal fork was in the works.TrueCrypt Developer “David”: Said “Bitlocker is ‘good enough’ and Windows was original ‘goal of the project.’ ”.Steven Barnhart: “Also said no government contact except one time inquiring about a ‘support contract.’ ”.Steven Barnhart: “I asked and it was clear from the reply that "he" believes forking's harmful because only they are really familiar w/code.”.Steven Barnhart (Paraphrasing): Developer “personally” feels that fork is harmful: “The source is still available as a reference though.”.We worked hard on this for 10 years, nothing lasts forever.” Steven Barnhart wrote to an eMail address he had used before and received several replies from “David.” The following snippets were taken from a twitter conversation which then took place between Steven Barnhart and Matthew Green TrueCrypt Developer “David”: “We were happy with the audit, it didn't spark anything. To excerpt a key part of that article: And then the TrueCrypt developers were heard from. Yes, Virginia, TrueCrypt is still safe to use.