What the warning by developers means is, in the event a vulnerability
   would be found in Truecrypt, no one would be there to fix it.
   Except for the entire open source community who would publish dozens of
   articles
   "here's how to fix the vulnerability in source code before recompiling
   it" accompanied with
   warnings "doing this breaks the truecrypt licence". This is true, and
   you might be in trouble
   in case the anonymous developers want to stop being anonymous and
   prosecute you across
   different jurisdictions. So, unlikely. Also read these:
   [1]http://istruecryptauditedyet.com/
   [2]http://blog.cryptographyengineering.com/2015/04/truecrypt-report.htm
   l
   [3]https://www.grc.com/misc/truecrypt/truecrypt.htm
   I heard TC uses insufficiently low iteration count for PBKDF2? -- this
   doesn't change the fact
   a high entropy passphrase (>128bits) remains unbreakable in feasible
   time.

   On 24.07.2015 17:46, Yush Bhardwaj wrote:

   BitLocker is better or I should try something else ?
   WARNING: Using TrueCrypt is not secure
   [4]http://krebsonsecurity.com/2014/05/true-goodbye-using-truecrypt-is-n
   ot-secure/
   [5]http://truecrypt.sourceforge.net/
   Yush Bhardwaj

References

   1. http://istruecryptauditedyet.com/
   2. http://blog.cryptographyengineering.com/2015/04/truecrypt-report.html
   3. https://www.grc.com/misc/truecrypt/truecrypt.htm
   4. http://krebsonsecurity.com/2014/05/true-goodbye-using-truecrypt-is-not-secure/
   5. http://truecrypt.sourceforge.net/