![]() ![]() TrueCrypt is pretty much just as good as it was before this happened. The last time TrueCrypt was updated was two years ago - it's stable software that doesn't need constant tweaking, so the developers bowing out is not a problem.Ĭhances are, someone will either fork TrueCrypt (version 3.1 of the TrueCrypt license seems to make this a legitimate possiblity) or create a replacement, possibly using the same container format. Despite the "security concerns" expressed in the TrueCrypt page, which were clearly a joke, there's no reason to think TrueCrypt has any significant vulnerabilities at this time, and the second phase of the audit will take place as scheduled. I've said this before in a few places, and it's (semi-) relevant here, but I really think people need to relax about replacing TrueCrypt.
0 Comments
Leave a Reply. |