VeraCrypt version 1.18a
idrassi
released this
19 Aug 07:55
·
1783 commits
to master
since this release
Binaries for Windows, Linux and MacOSX are available at Launchpad, Sourceforge and Codeplex
Changes between 1.17 and 1.18a (17 August 2016) :
- All OSs:
- Support Japanese encryption standard Camellia, including for Windows system encryption (MBR & EFI).
- Support Russian encryption and hash standards Kuznyechik, Magma and Streebog, including for Windows EFI system encryption.
- Windows:
- Support EFI Windows system encryption (limitations: no hidden os, no boot custom message)
- Fix TrueCrypt vulnerability allowing detection of hidden volumes presence(reported by Ivanov Aleksey Mikhailovich, alekc96 [at] mail dot ru)
- Enhanced protection against dll hijacking attacks.
- Fix boot issues on some machines by increasing required memory by 1 KiB
- Add benchmarking of hash algorithms and PRF with PIM (including for pre-boot).
- Move build system to Visual C++ 2010 for better stability.
- Workaround for AES-NI support under Hyper-V on Windows Server 2008 R2.
- Correctly remove driver file veracrypt.sys during uninstall on Windows 64-bit.
- Implement passing smart card PIN as command line argument (/tokenpin) when explicitly mounting a volume.
- When no drive letter specified, choose A: or B: only when no other free drive letter is available.
- Reduce CPU usage caused by the option to disable use of disconnected network drives.
- Add new volume ID mechanism to be used to identify disks/partitions instead of their device name.
- Add option to avoid PIM prompt in pre-boot authentication by storing PIM value unencrypted in MBR.
- Add option and command line switch to hide waiting dialog when performing operations.
- Add checkbox in "VeraCrypt Format" wizard GUI to skip Rescue Disk verification during system encryption procedure.
- Allow files drag-n-drop when VeraCrypt is running as elevated process.
- Minor GUI and translations fixes.
- Linux:
- Fix mount issue on Fedora 23.
- Fix mount failure when compiling source code using gcc 5.x.
- Adhere to XDG Desktop Specification by using XDG_CONFIG_HOME to determine location of configuration files.
- MacOSX:
- Solve compatibility issue with newer versions of OSXFuse.