VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
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
2019-10-03Windows: If Secure Desktop is started and random generator was not ↵Mounir IDRASSI1-53/+70
initialized before us, then stop random generator after we finish in order to avoid consuming CPU because of periodic fast poll thread. Next time a critical operation that requires RNG is performed, it will be initialized again. We do this because since the addition of secure desktop support, every time secure desktop is displayed, the RNG fast poll thread was started even if the user will never perform any critical operation that requires random bytes.
2019-10-03Windows: Add function RandinitWithCheck to detect if random generator was ↵Mounir IDRASSI2-1/+14
already initialized before our call or not
2019-10-03Windows: Use Jitterentropy RNG only in SlowPoll call and not in FastPoll ↵Mounir IDRASSI1-13/+0
since the it consumes too much CPU and FastPoll requires fast and minimal entropy gathering
2019-10-03'#define VERSION_STRING XXX' must come before '#define VERSION_STRING_SUFFIX ↵El Mostafa Idrassi1-3/+3
YYY' (#506) in order for 'export TC_VERSION := $(shell grep VERSION_STRING ../Common/Tcdefs.h | head -n 1 | cut -d'"' -f 2)' in 'src/Main/Main.make' to actually return the version rather than '-CustomEFI'.
2019-10-02Linux/MacOSX:check that the requested size of file container is less than ↵Mounir IDRASSI4-2/+13
available disk free space. Add a CLI switch to disable this check.
2019-10-02Utilize $(BASE_DIR) in the install targets rather than $(PWD) and $(CURDIR) ↵Unit 1931-63/+63
(#472) As $(PWD) is not always the expected value and can result in failing the target.
2019-10-02Allow $(ARCH) to be defined during build (#471)Unit 1931-1/+1
This can be useful when crossbuilding or building in a chroot where using uname -m would cause the wrong compiler options.
2019-10-02Align section types of Whirlpool_C and SHA256_K (#479)Hans-Peter Jansen1-1/+1
in order to fix LTO linking. After switching to LTO for openSUSE Tumbleweed, veracrypt build failed with: [ 185s] ../Crypto/Whirlpool.c:105:45: error: 'Whirlpool_C' causes a section type conflict with 'SHA256_K' [ 185s] 105 | CRYPTOPP_ALIGN_DATA(16) static const uint64 Whirlpool_C[8*256+R] CRYPTOPP_SECTION_ALIGN16 = { [ 185s] | ^ [ 185s] ../Crypto/Sha2.c:321:34: note: 'SHA256_K' was declared here [ 185s] 321 | CRYPTOPP_ALIGN_DATA(16) uint_32t SHA256_K[64] CRYPTOPP_SECTION_ALIGN16 = { [ 185s] | ^ [ 185s] lto-wrapper: fatal error: g++ returned 1 exit status Aligning section types of Whirlpool_C and SHA256_K fixes this.
2019-10-02Windows: Add support for /nosizecheck switch in Format command line file ↵Mounir IDRASSI1-1/+1
container creation
2019-10-02Increment version to 1.24-Beta6Mounir IDRASSI18-32/+36
2019-10-01Windows Driver: Disable Hibernation when RAM encryption is enabled since we ↵Mounir IDRASSI1-0/+6
can't resume from Hibernation without RAM encryption keys (a chicken and egg situation)
2019-09-30Windows: when periodic update of device is disabled, use SetupAPI to list ↵Mounir IDRASSI1-1/+3
disks on demand instead of testing all disks to reduce CPU usage.
2019-09-30Windows: resize VeraCrypt Format Wizard and Mount Options dialogs to fix ↵Mounir IDRASSI3-297/+295
some text truncation issues with non-English languages.
2019-09-29Windows: Update the encoded hash of the code signing certificate used to ↵Mounir IDRASSI1-6/+6
verify the integrity of binaries.
2019-09-29Windows: update signing script to use newly issued IDRIX SHA-1 code signing ↵Mounir IDRASSI5-62/+33
certificate.
2019-09-29Windows: Add latest 1.24 EFI bootloader files that are signed by Microsoft ↵Mounir IDRASSI12-0/+0
that come with the following modifications: - Fix issue that was preventing Streebog hash from being selected manually during Pre-Boot authentication - Ensure that the correct Windows bootloader is executed when the user press ESCAPE - make the rescue disk boot machine directly from disk if "VeraCrypt" folder is missing. This make it easy to create a bootable disk for VeraCrypt from the rescue disk by just removing or renaming its "VeraCrypt" folder.
2019-09-29Windows: Use periodic update of connected devices only if there is a ↵Mounir IDRASSI4-55/+101
Favorite that uses VolumeID. Add command option to disable the period update of devices.
2019-09-27Windows: fix another typo in code comment (hopefully last one!)Mounir IDRASSI1-1/+1
2019-09-27Windows: fix typo in code commentMounir IDRASSI1-1/+1
2019-09-26Windows: Fix sporadic keyboard issue in Secure Desktop for password dialog ↵Mounir IDRASSI3-2/+12
by not using the trick to put it reliably in foreground. The trick is based on a emulation of ALT+TAB but sometimes ALT key would remain pressed in case of Secure Desktop making it impossible to type the password (a workaround was to press CTRL key which reset the state of ALT key)
2019-09-25Windows: Add two missing UI strings to XML translation files so that they ↵Mounir IDRASSI2-1/+3
can be localized correctly
2019-09-25Windows: Disable the Keyfiles button in system encryption wizard since we ↵Mounir IDRASSI1-1/+2
don't support them yet.
2019-09-24Linux/OSX: make CLI switch --import-token-keyfiles compatible with ↵Mounir IDRASSI1-3/+12
Non-Interactive mode by using keyfiles passed as arguments and check the Non-Interactive mode switch.
2019-09-24Windows: fix HourGlass cursor showing up in main UI after launching disk ↵Mounir IDRASSI1-4/+0
decryption wizard/
2019-09-23Fix build error of UEFI bootloader caused by latest changes that introduced ↵Mounir IDRASSI2-1/+3
ChaCha20 and T1HA algorithms and which are not present nor used in UEFI bootloader
2019-08-26Windows: fix compilation error of legacy MBR bootloader caused by missing ↵Mounir IDRASSI1-1/+1
intrin.h header
2019-06-06Some cleanup related to "Invalid characters..." on mount issue. (#453)Alexander Karzhenkov1-23/+3
* Revert previous commit * Fix "Invalid characters..." issue by not using "foreach" macro The "foreach" macro creates a copy of the container. This copy is destroyed immediately after the iteration is completed. C-strings pointers passed to the local array were invalidated with destroying of "std::string"s contained in the copy.
2019-06-06Fix password-only example in help text (pim missing) (#438)Dany Shaanan1-1/+1
2019-03-21Linux: Fix compilation error caused by wrong include of "intrin.h"Mounir IDRASSI1-3/+1
2019-03-09Increment version to 1.24-Beta5Mounir IDRASSI17-31/+31
2019-03-09Windows Driver: fix BSOD when mounting outer volume with hidden volume ↵Mounir IDRASSI1-1/+1
protection if RAM encryption is enabled
2019-03-09Increment version to 1.24-Beta4 and update release notes to clarify that ↵Mounir IDRASSI17-31/+31
password length increase applies only to non-system volumes.
2019-03-08Windows: inform user that RAM encryption setting requires reboot to take effectMounir IDRASSI1-1/+23
2019-03-08Windows Driver: fix BSOD when mounting hidden volume if RAM encryption is ↵Mounir IDRASSI1-4/+5
enabled
2019-03-04Windows: Update signed drivers for 1.24-Beta3Mounir IDRASSI5-1/+1
2019-03-03Windows Driver: Add IOCTL code to query RAM encryption status in VeraCrypt ↵Mounir IDRASSI2-0/+13
driver