Most of my drives are encrypted with Truecrypt. As you probably know, Truecrypt support has ended, but a program called Veracrypt, based on the Truecrypt code, is attempting to replace it.
A new version of Veracrypt came out last month that supports mounting Truecrypt volumes, but losing my data would be a disaster, so I don't want to commit to Veracrypt wholesale until it has a longer track record. And I see no reason to convert my Truecrypt drives to Veracrypt, since they work fine now.
Also, Veracrypt only supports TC drives back to version 6, and I'm pretty sure some of mine are older than that.
What I would like to do is start using Veracrypt with whatever new encrypted containers or partitions I create from now on, but since I typically have three or four physical drives mounted at once, that would mean running it concurrently with Truecrypt.
Since both programs intercept read and write requests at a very low level, would they interfere with each other?
Also, can anyone share their experience in converting TC drives to VC?
Thank you.
A new version of Veracrypt came out last month that supports mounting Truecrypt volumes, but losing my data would be a disaster, so I don't want to commit to Veracrypt wholesale until it has a longer track record. And I see no reason to convert my Truecrypt drives to Veracrypt, since they work fine now.
Also, Veracrypt only supports TC drives back to version 6, and I'm pretty sure some of mine are older than that.
What I would like to do is start using Veracrypt with whatever new encrypted containers or partitions I create from now on, but since I typically have three or four physical drives mounted at once, that would mean running it concurrently with Truecrypt.
Since both programs intercept read and write requests at a very low level, would they interfere with each other?
Also, can anyone share their experience in converting TC drives to VC?
Thank you.