Still, the very sudden and unexpected announcement is definitely worth some amount of skepticism. A key difference between TrueCrypt and Windows XP however, is that compatible alternatives may still be developed and updated since TrueCrypt is open-source software. If they did choose to do that, then TrueCrypt would in fact become insecure in very much the same way as Windows XP now is - any newly discovered security vulnerabilities would not be patched.
#Truecrypt replacement 2016 full
The current required Windows build environmentĭepends on outdated build tools and software packages that are hard to get from trustworthyĪll of this, along with the two-year lapse in new releases and lack of full support for the latest OSs, does lend to the easy belief that TrueCrypt's team may indeed be throwing in the towel.
This will make future bugs harder to find and correct. The report also said the source code "did not meet expected standards for secure code".ĭue to lax quality standards, TrueCrypt source is difficult to review and The first phase of the TrueCrypt audit, covering the bootloader and Windows kernel drivers, turned up less than a dozen vulnerabilities - the worst of which were rated as "Medium" severity. For anyone else, it would probably be preferable to wait until this whole mess is cleared up. Many Windows 8 users who used to rely on TrueCrypt are probably already migrated to Bitlocker for whole-disk encryption, so moving the rest of their TrueCrypt-protected data (if they haven't already) is a logical next step anyway. Also no apparent efforts have been made to support whole-disk encryption on Windows 8, which even older than TrueCrypt 7.1a if you count in the publicly-available pre-release versions of the former. That said, it is noteworthy that the latest version of TrueCrypt (before the 7.2 version that's now posted) is over two years old. Speculation runs rampant as to whether it's a defacement or official retirement.
0 kommentar(er)
