Earlier quoted context omitted.
They're your most realistic option right now. They are actively developing it and added things like newer algorithms (e.g. SHA2). There's CipherSched but that is basically a completely new program/rewrite which is very far from done. However, I don't agree with VeraCrypts choices. They've changed several things that make mounting slow (0,5s -> 10s), which is annoying, especially if you mistype the password. Providing…
This is an odd conclusion to come to. Are there a lot of users of True/Veracrypt that don't understand this? I guess I just don't see my grandparents using either of these packages, and I can't imagine a lot of "normal" users "trying out" a new encryption program.
The passphrase to one of my TrueCrypt volumes is around 30 characters long. It's not completely random, so let's say it only has 2 bits of entropy per character. That's 60 bits total. A brute-force attack would take an average of 2^59 guesses before it succeeds.
At 10 seconds per guess, we're looking at approximately 180 billion years to crack my passphrase. Even if you devoted a million computers to the job (as an extremely well-funded adversary might do), it would still take 180,000 years.
If you weakened the PBKDF to take 1 second instead, it would take 18,000 years to crack my relatively weak passphrase using a million computers. That's still long enough that I don't care at all. Moreover, if I were really paranoid, I can easily bring it back to the 180,000-year mark (or more) by adding a few more characters to my passphrase, which would only take another second to type. So why wait 10 seconds?