Incompatibilities to Truecrypt

[Anonymous]

You said quote: "VeraCrypt storage format is INCOMPATIBLE with TrueCrypt storage format"

Does that mean VeraCrypt can't read / convert existing TrueCrypt containers?

Also the TrueCrypt source is known for its sloppy coding. Did the source got an overhaul?

[Mounir IDRASSI]

Yes, VeraCrypt can't read/convert TrueCrypt containers. But it's possible to implement a tool that converts TrueCrypt containers (7.x at least) to VeraCrypt since the format of volume header is almost the same.
For now, there are others development priorities but eventually we can implement such tool.

On the other hand, I don't find TrueCrypt source coding sloppy at all. But I respect your opinion. If you look at projects like OpenSSL, you'll see real sloppy coding!
That being said, the source will need to be adapted to introduce new features and it will be the opportunity for a source overhaul.

[Gvozden]

Such a converter would be very nice.

[Anonymous]

I found your fork (do you have found a solution for the license problem with TC? or do you take a risk with your fork?) a few minutes ago and I am willing to try it out, but not beeing able to use my old TC containers and partitions is keeping me away from it.

It would be really nice if you could implement a converting tool.

Thanks!

[Mounir IDRASSI]

For the license, we are sticking to the terms of the original TrueCrypt license by removing all TrueCrypt references and putting VeraCrypt under TrueCrypt license. Our understanding is that this is OK but others may have another interpretation.
So for now, we are going forward and if we encounter any license issue in the future, we'll deal with it on time.

We understand you need for a converting tool. Its development is delayed because of our limited resources but we will do our best to make it happen before the end of this year.

[Joseph]

I think conversion tool is not so vital: mount your old container via TC and open new conatiner with VC and copy/pass the content... its so easy in my opinion.

In my case this method gave me the possibility to erase old files that were not more so important to be kept in the container :)

So, I think, who mantains the VC project can concentrate himself on more important things.

[Anonymous]

I installed Veracrypt to an external hard drive successfully. I unplugged it and then plugged it back in, I was given an option to format the disk and erase everything. I said yes and my drive was erased completely. Is there an option where the format prompt does not pop up? or you need a password to format the hard drive? this is very dangerous in the case of accidental format or intentional by someone who is not the owner of the disk. In other words, it is too easy to erase the contents of the drive. Luckily, I only had test copy files on the hard drive.

[Mounir IDRASSI]

Unfortunately, there is no way protect against the destruction of an encrypted drive or volume. No encryption software, free or paying, can protect against that.

If you need protection against such scenario, the only way is to use a hard drive that incorporate a password protection: this way, the hard drive is not usable under Windows until you enter a password (popular USB hard drive offer this option)

This password is internal to the hard drive and it is not intended for encryption but merely to protect against unauthorized access.
If you combine this password with VeraCrypt encryption using a different password, you can protect against accidental formatting of your encrypted drive.

[Anonymous]

Personally, I think it is better that veracrypt remains incompatible with truecrypt, for safety reasons and as an additional protection against brute-forcing. For example, you can use one for system encryption and the other for external storage / file containers. This way if an attacker gains access to your equipment, they will see the bootloader and simply assume you encrypted all your removable drives with the same software, as there is no way to tell which program has been used in a full disk encryption where no bootloader is present.

[Anonymous]

If I create an encrypted container using your nightly build e.g. beta f, will it still be compatible with future VeraCrypt releases as far as you can see at this point or will you only guarantee for a major version release?

[Mounir IDRASSI]

Yes, containers created with the 1.0f-BETA will be compatible with future VeraCrypt releases.

[Seeker]

Hello - We have just installet VeraCrypt (ver 1.24) and we have External Hard drives that are encypted with TruCrypt. Is there a way to mount the TruCrypt external hard drives with VeraCrypt and also be able to read the data?
Thanks for your Assistance

[Enigma2Illusion]

Always have backups of your data due to hardware failure, software issues or user error can cause loss of access to the encrypted volumes and unecrypted drives.

https://www.veracrypt.fr/en/TrueCrypt%20Support.html

https://www.veracrypt.fr/en/Converting%20TrueCrypt%20volumes%20and%20partitions.html

[Seeker]

Enigma2illusion,

Thanks for the help! Wil try this out a bit later!