| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We always using Unicode functions to interact with UI. We convert UTF8 string to UTF16 and vis-versa.
Overwrite input string instead of using resize that caused old test to remain.
Fix case of readOnly by using correct message.
change position of OK/cancel button to match other dialogs.
Activate translation on this dialog.
|
|
|
|
with ERROR_INVALID_FUNCTION
Proposed by @kriegste on https://github.com/veracrypt/VeraCrypt/issues/360
|
|
fixed by Mattoje #1417
|
|
protection doesn't work on Linux
In the code we also enable it for TC_WINDOWS but actually we don't use wxWidgets for Windows build.
|
|
Veracrypt currently appears in screenshots and screen captures,
which can unintentionally expose sensitive information, such as
the fact that Veracrypt is running or the location of your volumes.
Both Windows and macOS offer mechanisms to exclude specific windows
from being captured. While not foolproof, this is a useful preventative
measure. The method is a no-op for Linux/FreeBSD.
For more details on the wxWidgets API, see:
https://docs.wxwidgets.org/3.2/classwx_top_level_window.html#a337b9cec62b0cbd3b1b1545a83270f64
|
|
not defined.
we now report that EFI is not support only when GetFirmwareEnvironmentVariable fails with error ERROR_INVALID_FUNCTION.
Proposed by @kriegste on https://github.com/veracrypt/VeraCrypt/issues/360
|
|
version, control packaging)
Based on proposal by @Mattoje in https://github.com/veracrypt/VeraCrypt/issues/1417
|
|
|
|
Visual Studio 2019
We also enable Control Flow Guard and Spectre Mitigation
|
|
path
|
|
removed instead
This started to cause issues after latest changes to disable privileges when they are no more needed.
Because of the bug, the privileges could not be enabled again because they were wrongly removed.
|
|
|
|
scheduling removal on reboot if needed
|
|
new version
We use Checksum attribute so that MSI compares hash of file on disk with expected value and trigger overwrite if they differ
|
|
left from old versions. Increment version to 1.26.15.
|
|
REBOOT=ReallySuppress specified and a reboot is required
In this case, installation was done by the customer action VC_CustomAction_DoChecks was returning the error ERROR_INSTALL_FAILURE (1603)nevertheless.
Now we return success code correctly.
|
|
|
|
|
|
with langid one of the predefined language identifiers)
|
|
changing password of volumes
|
|
This reverts commit ce9537f2b847b9b3b89e8dfca377d2659b3f02fc.
|
|
|
|
Language.xx-yy.xml format)
|
|
This prevents the inadvertent inclusion of XML file artifacts (e.g., Language.fr - Copy.xml) during the creation of installers.
|
|
|
|
messages in case of failure.
Now we accept the possibility of BootOrder EFI variable to be empty in order to try to solve issues on some PCs.
|
|
Windows 10/11 SDK
We set Windows 8 as minimum API support fir Visual Studio 2015 and newer.
Closes #1398
|
|
|
|
|
|
|
|
and old algorithms.
|
|
|
|
|
|
|
|
password entry
Cause seems to be IME as documented in KeePass project (https://keepass.info/help/kb/sec_desk.html#ime). We use the same approach as KeePass to disable IME in Secure Desktop.
This commit also add few changes:
- we switch to secure desktop only if SetThreadDesktop succeeds
- we call SwitchDesktop to switch to original desktop only if we actually succeeded in displaying secure desktop
|
|
* Add Norwegian Bokmål translation
* Fix Norwegian Bokmål translation
|
|
drivers.
|
|
If vulnerability detected, a warning message is displayed during mount or backup/restore header, and changing the password is disallowed since it will not change the master key.
|
|
|
|
|
|
The class AdminPasswordRequestHandler was defined in several places in the same namespace and the linker was picking up one definition for constructor and the other one when calling virtual method.
Now we use different named for different implementations.
|
|
* Documentation: Update QR codes and logos
* Add QR codes in 200x200 resolution
|
|
|
|
Github action by using builtin GITHUB_TOKEN
|
|
* Linux/MacOSX: during build, fallback to /tmp if wxWidgets sources not found in parent directory
* Linux: Add Github workflow to build .deb files and test generated binaries
* Linux: fix wrong wxWidgets extract path in yaml
* fix: fix wrong wxWidgets extract path in yaml
* Linux: harmonize content of test volumes and update Github workflow for this
* Fix corrupted test container
* Linux: optimize Github workflow by caching wxBuildConsole and wxBuildGUI folders
We also modify build script to detect the presence of wxBuildConsole and wxBuildGUI folders and reuse them
* Remove files mistakenly added
* Linux: Fix wrong test for Github workflow
* Linux: use static build of wxWidgets for GUI in Github workflow
* Linux: upload also .deb SHA256SUM file if it is generated in Github workflow
* Linux: fix detection logic of parent folder in build scripts
* Github workflow: add build_cmake_deb.sh as trigger to build-linux.yml
* Github workflow: add wxWidgets source code to the cache of workflow
|
|
for generic GUI installer
|
|
Reported on https://sourceforge.net/p/veracrypt/discussion/technical/thread/90f967e642
reference: https://grsecurity.net/toolchain_necromancy_past_mistakes_haunting_aslr
script to check: https://github.com/opensrcsec/paxtest/blob/master/contrib/check_align.sh
|
|
Full Xcode application which can take up-to 40GB of disk space is not
necessary for building VeraCrypt, rather the CommandLineTools for XCode
are sufficient which only take few gigabytes. Instead of hardcoding the SDK
location, use xcrun --show-sdk-path to support also the CommandLineTools
instance.
The reason for switching the logic for the XCode version is because the
xcodebuild will not report a correct XCode version for the CommandLineTools,
thus it can't be relied for whether to use the -Wl,-ld_classic flags.
Instead, we can just check the ld version in use in the active developer
directory, and see whether we are using dyld (the new) or ld64 (the old).
|
|
|
