VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2019-10-27Windows: Only update boot configuration on disk if the user actually changed ↵Mounir IDRASSI1-25/+29
something in the UI
2019-10-27Windows: code refactoring and convert NTSTATUS error code to WIN32 ↵Mounir IDRASSI2-41/+26
equivalent before displaying error message.
2019-10-27Windows: Make EFI System Encryption PostOOBE code more robust to failure to ↵Mounir IDRASSI2-92/+104
access "\\\\?\\GLOBALROOT" disk namespace
2019-10-27Windows: Update EFI NVRAM variable only if changed or doesn't exist and add ↵Mounir IDRASSI3-12/+27
configuration to force setting EFI BootNext to veraCrypt bootloader before each shutdown
2019-10-26Windows: Restore veraCrypt boot meny entry for system encryption more often, ↵Mounir IDRASSI1-7/+16
especially during PostOOBE calls, and handle additional corner cases.
2019-10-26Linux: Add build script for OpenSUSEMounir IDRASSI2-2/+72
2019-10-26MacOSX: Update build script and Makefile to correctly build Legacy version ↵Mounir IDRASSI2-22/+91
of VeraCrypt that targets OSX 10.7+.
2019-10-26MacOSX: fix truncated algorithms description in the Encryption Options page ↵Mounir IDRASSI2-0/+24
of the volume creation wizard, which happened after moving to wxWidgets 3.1.2
2019-10-26MacOSX: use wxWidgets 3.1.2 for the legacy build which is now done with SDK ↵Mounir IDRASSI1-4/+5
10.9 while still targeting OSX 10.7.
2019-10-25Set release date of 1.24-Hotfix1 to October 25th.Mounir IDRASSI1-1/+1
2019-10-25Windows: Fix test of GetPrivateProfileString output since this function ↵Mounir IDRASSI1-1/+1
discards double quotation marks
2019-10-25Windows: only update MBR first 512 bytes if they have changed and don't ↵Mounir IDRASSI1-30/+45
update full MBR bootload in case of PostOOBE
2019-10-25Windows: for system encryption case, also perform automatic fix of boot ↵Mounir IDRASSI1-14/+10
configuration if MBR boot used and not only EFI.
2019-10-25Windows: Avoid unnecessarily update of system encryption SetupConfig related ↵Mounir IDRASSI1-4/+53
files if there content didn't change
2019-10-24MacOSX: Add dedicated installer for legacy version that targets OSX 10.7+ ↵Mounir IDRASSI2-27/+1106
and update requirement for new installer to be OSX 10.9+ and 64-bit only.
2019-10-24MacOSX: fix typo in MacOSX legacy build scriptMounir IDRASSI1-1/+1
2019-10-24Linux/MacOSX: Better approach to avoid that jitterentropy code is optimized ↵Mounir IDRASSI3-6/+16
by the compiler
2019-10-24Increment version to 1.24-Hotfix1Mounir IDRASSI11-28/+28
2019-10-24Linux: set version explicitly in CMakeLists.txt instead of relying on ↵Mounir IDRASSI1-15/+5
parsing of Tcdefs.h which can be erroneous
2019-10-24Windows: display prompt to upgrade Rescue Disk when installing 1.24 version ↵Mounir IDRASSI1-1/+1
since it adds functionality and it has better support for fix boot issues.
2019-10-23Linux/MacOSX: Add missing JitterEntropy implementationMounir IDRASSI4-4/+39
2019-10-23Windows: A Quick Expand option to VeraCrypt Expander to allow quicker ↵Mounir IDRASSI5-12/+95
expansion of file containers after warning about security issues associated with it.
2019-10-20Increment version to 1.23-Hotfix1-PreviewMounir IDRASSI12-29/+29
2019-10-20Windows: Avoid unnecessary write operations when copying/modifying EFI ↵Mounir IDRASSI2-6/+126
bootloader files in order to avoid leaking modification timestamp
2019-10-20Windows: add more checks to correctly identify Microsoft original bootloader.Mounir IDRASSI1-3/+24
2019-10-20Windows: Add checks that the System Favorites service is running. Warn user ↵Mounir IDRASSI6-4/+80
if he enabled option to clear RAM encryption keys and the service is stopped.
2019-10-20Windows: resize UI elements of random collection step in Format wizardMounir IDRASSI1-8/+7
2019-10-19MacOSX: Support APFS for creating volumes.Mounir IDRASSI5-0/+14
2019-10-18Windows: make VeraCrypt Expander able to resume expansion of volumes whose ↵Mounir IDRASSI2-7/+18
previous expansion was aborted before it finishes
2019-10-18Windows: handle case of DcsProp configuration file for EFI system encryption ↵Mounir IDRASSI2-30/+93
contains wrong "ActionSuccess" entry that points towards bootmgfw.efi which is now our bootloader and not Microsoft one.
2019-10-17Linux: Workaround for gcc 4.4.7 bug under CentOS 6 that causes VeraCrypt ↵Mounir IDRASSI1-0/+14
built under CentOS 6 to crash when Whirlpool hash is used.
2019-10-17Linux: fix compilation error under CentOS 6Mounir IDRASSI1-0/+1
2019-10-16Small GUI enhancements (#521)El Mostafa Idrassi2-12/+12
2019-10-16Fixed drag and drop not showing correct path, specifically under GTK-3. (#520)El Mostafa Idrassi3-6/+0
2019-10-15MacOSX: Enhanced Makefile and build script (#519)El Mostafa Idrassi2-13/+14
Added new variable 'VC_OSX_SDK' to differentiate between the OSX minimum target and the SDK to use for building.
2019-10-15Fixed buttons not being correctly aligned (#518)El Mostafa Idrassi2-9/+12
2019-10-14MacOSX: Add build scripts and modifications to linking against wxWidgets ↵Mounir IDRASSI6-23/+183
3.1.2 for non legacy build targeting OSX 10.9+
2019-10-14Windows: Fix regression that causes system favorites not to mount if ↵Mounir IDRASSI1-1/+9
VeraCrypt 1.24 is freshly installed and not updated.
2019-10-11MacOSX: Fixed devices / partitions not showing in the device selection ↵El Mostafa Idrassi1-6/+34
dialog (#516) To get the size of each device / partition on the system, the method 'GetDeviceSize()' in 'src/Core/Unix/CoreUnix.cpp' first opens the device / partition using 'open()' function to get a File Descriptor, then retrieves its size using this File Descriptor. Starting OS X 10.11 ("El Capitan"), a feature called "System Integrity Protection (SIP)" or less formally, "rootless mode" has been added. This feature blocks access to certain critical aspects of the OS and Hardware by 3rd-Party programs. Specifically, low-level access to the system disks, devices and partitions is forbidden ; namely functions like 'open()' for instance fail with the error code : "EPERM = Operation Not Permitted". Therefore, for system devices / partitions, 'GetDeviceSize()' fails because of the failure of the 'open()' function, and throws an exception, which is then caught inside the method 'GetHostDevices()' in '/src/Core/Unix/FreeBSD/CoreFreeBSD.cpp' : this leads to the size of the device / partition being set to '0'. Therefore, in the constructor of 'DeviceSelectionDialog' in 'src/Main/Forms/DeviceSelectionDialog.cpp', when the size of a device is '0', the whole device is skipped, leading to all of its partitions not being treated or shown, even though some of these partitions may have a size which is != 0. This commit fixes the issue by : 1 - First, checking whether the device size is '0'. If it is the case, the code loops through all the devices partitions : if there is at least one partition with a size != 0, the device is not skipped. Otherwise, it is. 2 - Then, if the size of the device is '0', the size of the device is not shown to avoid confusing the user. Also, since the device is not usable, the 'OK' button is not active when the device is selected. 3 - Finally, if a partition's size is '0', it is not shown since it is not usable : we cannot open it. Signed-off-by: El Mostafa IDRASSI <el-mostafa.idrassi@prestalab.net>
2019-10-08Linux/FreeBSD: Use of 'sudo -n uptime' command to check whether user has an ↵El Mostafa Idrassi1-0/+37
active 'sudo' session instead of the use of a 'dummy' password. (#513) Signed-off-by: El Mostafa IDRASSI <el-mostafa.idrassi@prestalab.net>
2019-10-07Updated and fixed build and packaging scripts. (#512)El Mostafa Idrassi4-45/+130
Now, under Debian 10+ and Ubuntu 18.04+, we link against the GTK-3 version of wxWidgets (libwxgtk3.0-gtk3-0v5). Under Debian 9- and Ubuntu 16.04, we link against the GTK-2 version of wxWidgets (libwxgtk3.0-0v5) which is the only one available. Also, we now have 2 separate RPM scripts : 'build_cmake_rpm_gtk2.sh' which builds wxWidgets and links it against GTK-2, then links VeraCrypt against 'gtk2' package (typically to be used under CentOS 6) and 'build_cmake_rpm_gtk3' which builds wxWidgets and links it against GTK-3, then links VeraCrypt against 'gtk3' package (typically to be used under CentOS 7+).
2019-10-06MacOSX: fix link error under Xcode 4.6.3VeraCrypt_1.24Mounir IDRASSI2-3/+7
2019-10-06Linux/FreeBSD: change location of documentation from ↵Mounir IDRASSI4-4/+6
/usr/share/veracrypt/doc to the standard /usr/share/doc/veracrypt
2019-10-06Increment version to 1.24Mounir IDRASSI10-16/+16
2019-10-05Linux: modifications to cmake files to use GTK3 on CentOS and change ↵Mounir IDRASSI3-11/+11
packages names
2019-10-05Linux: Add option in Makefile to use GTK3 in VeraCrypt static buildMounir IDRASSI1-1/+7
2019-10-04Linux: Added CMake script for creating .DEBs and .RPMs for VeraCrypt using ↵El Mostafa Idrassi5-0/+441
CPack, and shell scripts which build then package VeraCrypt under CentOS and Debian/Ubuntu. (#511) The DEB script builds VeraCrypt and links it against wxWidgets that comes with the distribution. The RPM script awaits for wxWidgets-3.0.4 source code which it builds then links VeraCrypt statically to it. Both scripts create the corresponding package after the build.
2019-10-04Linux : Added missing 'mkdir' before installing in case $DESTDIR does not ↵El Mostafa Idrassi1-0/+2
exist (#510)
2019-10-04Windows: Update libzip to version 1.5.2Mounir IDRASSI112-164/+247
2019-10-04Fix "error "SSSE3 instruction set not enabled" when compiling using GCC ↵El Mostafa Idrassi1-0/+2
version < 4.9 without -mssse3 option (SSSE3=1 when using make). (#507) Compiling with -mxxx defines the corresponding macro of the intrinsics. For example, -mssse3 defines __SSSE3__ macro to 1. In GCC versions < 4.9, it is not possible to use and call x86 intrinsics only at runtime without compiling the entire file with the -mxxx option. For example, if we want to call SSSE3 intrinsics without compiling with -mssse3, the macro __SSSE3__ is not defined. Therefore, when including <tmmintrin.h>, this results in "error "SSSE3 instruction set not enabled"" because of : #ifndef __SSSE3__ # error "SSSE3 instruction set not enabled" Since GCC 4.9, this has been fixed and it is possible to call x86 intrinsics from select functions in a file that are tagged with the corresponding target attribute without having to compile the entire file with the -mxxx option. This can be seen in <tmmintrin.h> which in recent versions (>= 4.9) contains : #ifndef __SSSE3__ #pragma GCC push_options #pragma GCC target("ssse3") #define __DISABLE_SSSE3__ Since SSSE3 is only used under Windows for ChaCha256, this can be fixed by preceding '#include <tmmintrin.h>' with #if defined (_MSC_VER) && !defined (TC_WINDOWS_BOOT). See https://gcc.gnu.org/gcc-4.9/changes.html