fokiplum.blogg.se - Github truecrypt

GITHUB TRUECRYPT FOR MAC
GITHUB TRUECRYPT SOFTWARE

The whole situation with TrueCrypt is just a bit off, none of it makes sense from our viewpoint. The TrueCrypt dev team was told by a government agency to add a backdoor to TrueCrypt.

Changes every "U.S." to "United States" (possibly irrelevant).Removed the clause requiring a link to or to say your code uses TrueCrypt.Added a bunch of messages saying the exact same thing on the website- TrueCrypt is insecure.Removed the ability to create encrypted volumes and drives.Has a lot of changes that appear to have been in development for a while, like an incomplete new version.

GITHUB TRUECRYPT FOR MAC

The directions for Mac encryption say to use "none".

The directions for Bitlocker migration are simply wrong (you should unencrypt before you go to bitlocker, but they say the reverse).

The directions for Bitlocker are only possible for the few people who use Ultimate and Enterprise versions of Windows, less then 20% of users.

There is a mention of the end of Windows XP support, and an incorrect date for its end of life, 5/2014 instead of 4/2014.

The main page has been replaced with instructions to switch to Bitlocker for Windows.

Now redirects to the SourceForge page for Truecrypt using a 301 permanent redirect.

The entire site redirects to the SourceForge project page.

Still has the same IP address of many years back DNS History for Truecrypt.

Sourceforge claims there is no suspicious activity on the admin account source.

Sourceforge changed its password policy 1 week before the incident source.

Signed keys were updated 3 hours before posting version 7.2 by an apparently legitimate source Sourceforge, Truecrypt account history rss version.

These are facts of what I have seen that may offer some insight into the cause of TrueCrypt's recent decision.

We worked hard on this for 10 years, nothing lasts forever."

GITHUB TRUECRYPT SOFTWARE

Is this really what happened though? I mean what about the panic stricken Bitlocker page and the mysterious method used to leave the software world? What about the refusal to let others build on the code that was nearly open-source? It still seems fishy, but we do have an answer from the dev at 1 more "I were happy with the audit, it didn't spark anything. He claims that he does not want anyone using the source code for the bootloader and the GUI because "that's harmful because only they are really familiar w/code". The dev claims to have just gotten tired of maintaining the program Truecrypt. 3.5 #5 - Government Trying to Smoke out DevelopersĪs per recent posts from Matthew Green and Steven Barnhart, it appears as though we have an answer.