Announcement: 1.19 Released

[Enigma2Illusion]

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.19/

NOTE: Removal of GOST89 (Magma) encryption algorithm. You can read the reasons at the link below.

https://veracrypt.codeplex.com/discussions/658561

[Natanji]

The EFS fix seems to only have partially fixed the problem.

Accessing files is now possible again, so I can move them around and all.

I can also encrypt files newly with EFS and they work fine.

But all my old files that were previously inaccessible (and remained so for the months while the EFS access was broken) now simply contain gibberish! Do you have any idea why this happens? The integrity of my files is at stake here... :(

[Mounir IDRASSI]

@Natanji:
I didn't have this EFS problem with old files during my tests. Just to clairy: you are able to copy and read newly created EFS files but existing EFS files have a bad content?
Are able to access you disk from another version of Windows to do tests?

[Natanji]

Yes, exactly: newly created EFS files seem to be fine and their content shows up as it should, but the previously existing ones have bad content now.

I could put my disk into a second computer, sure - what am I supposed to do there though, exactly?

[Enigma2Illusion]

Windows EFI: don't use optimized Serpent implementation for EFI bootloader because lack of C++ support in EDKII framework

Does this mean that if you use Serpent for system encryption algorithm that you will not get the performance optimized Serpent once your PC boots-up?

If using system encryption algorithm Serpent, will mounting other volumes using Serpent after the PC boots-up or using System Favorites result in using the slower Serpent implementation?

[Mounir IDRASSI]

The lack of Serpent optimization applies only to the EFI bootloader which handles on the fly decryption/encryption until Windows starts (it takes only few seconds).
Once Windows starts, VeraCrypt driver takes over EFI bootloader and so optimized Serpent implementation is used.
Basically, when running VeraCrypt on 64-bit Windows, Linux and MacOSX, users will notice a 2.5x speed gain.

[Enigma2Illusion]

Release notes missed the following:

Optimize performance of Twofish C implementation.

[Mounir IDRASSI]

The speed gain is not much (between 10% and 20% depending on CPU), that's why it was not mentionned.

[Unit 193]

It seems the source tarballs are also double gzipped, thus a normal tar xf won't do as you have to first gunzip it once.

[Mounir IDRASSI]

@Unit193: Indeed, there was an issue while creating the tar.gz from sources. The zip file is OK. Unfortunately, we'll have to live with it.

[Nanana]

How do I upgrade Veracrypt without data loss? Shall I decrypt my disk, delete veracrypt old version 1.18a and install 1.19?

[Enigma2Illusion]

For Windows, dismount any non-system encrypted volumes, download 1.19 and install. You will be prompted to reboot your system after installation. Do not defer the reboot!

EDIT:

https://veracrypt.codeplex.com/discussions/658844#post1486502

Re-encryption is needed only if you were using GOST89 cipher. No re-encryption is needed otherwise.

For system encryption, you will need to create a new Rescue Disk (zip for EFI and ISO for MBR) in order to have a Rescue Disk that uses the updated boot components.