Sourceforge project page: TrueCrypt stops in 5/2014
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think that is simply a statement that is true both now and forevermore (since support is stopped).
There _may_ be unfixed security holes now, either known or unknown. In a year that will still be true. So, The Statement That Never Requires Change(TM) is invoked.
Thanks for the dm-crypt reminder. I never got around to implementing truecrypt and now I never will. ;vD
I have a strong feeling that the site may be hacked, so don't trust it just yet. I mean why would they suddenly remove all previous truecrypt versions, and why right after the audit, which wasn't free.
I have a strong feeling that the site may be hacked, so don't trust it just yet. I mean why would they suddenly remove all previous truecrypt versions, and why right after the audit, which wasn't free.
Quote:
Significantly, TrueCrypt version 7.2 was certified with the official TrueCrypt private signing key, suggesting that the page warning that TrueCrypt isn't safe wasn't a hoax posted by hackers who managed to gain unauthorized access. After all, someone with the ability to sign new TrueCrypt releases probably wouldn't squander that hack with a prank. Alternatively, the post suggests that the cryptographic key that certifies the authenticity of the app has been compromised and is no longer in the exclusive control of the official TrueCrypt developers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.