Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.

TrueCrypt Discontinued, Compromised?

posted by LaminatorX on Thursday May 29 2014, @04:03AM   Printer-friendly
from the Another-one-bites-the-dust dept.

J053 writes:

The TrueCrypt website has been changed it now has a big red warning stating "WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues". They recommend using BitLocker for Windows 7/8, FileVault for OS X, or (whatever) for Linux. So, what happened? The TrueCrypt site says:

This page exists only to help migrate existing data encrypted by TrueCrypt. The development of TrueCrypt was ended in 5/2014 after Microsoft terminated support of Windows XP. Windows 8/7/Vista and later offer integrated support for encrypted disks and virtual disk images. Such integrated support is also available on other platforms (click here for more information). You should migrate any data encrypted by TrueCrypt to encrypted disks or virtual disk images supported on your platform.

Did the TrueCrypt devs (or SourceForge?) get a NSL? They are offering a "new" version (7.2), but apparently the signing key has changed and a source code diff seems to indicate a lot of the functionality has been stripped out. What's up?

 
This discussion has been archived. No new comments can be posted.
TrueCrypt Discontinued, Compromised? | Log In/Create an Account | Top | 91 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 4, Insightful) by RamiK on Thursday May 29 2014, @09:45AM

    by RamiK (1813) on Thursday May 29 2014, @09:45AM (#48648)

    To be fair, this also applied to China and Russia. Just stick to Made in EU open source encryption, communication equipment and operating systems until the ninth circuit bans NSLs. Right now, even if you trust a US based developer, he can't legally disclose backdoors and information he supplies to his government. So, just don't risk it.

    --
    compiling...
    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Informative=1, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   4  

  • (Score: 2) by AnythingGoes on Thursday May 29 2014, @09:45PM

    by AnythingGoes (3345) on Thursday May 29 2014, @09:45PM (#48927)

    That was the reason why OpenBSD was developed in Canada. Back then (before 1996 or so), it was illegal to export greater than 40bit encryption outside the US, so Theo refused to use any US resources to store OpenBSD.

    What is sad, is that the most tinfoil-hatted of us was finally revealed to be right!