Age | Commit message (Collapse) | Author | Files | Lines |
|
and not GTK3
|
|
that was causing volume headers to be corrupted.
|
|
exits if /q was specified in CLI. This done using the new switch "/signalExit" who must have a string parameter that must be the same as the one that will be specified for WAITFOR.EXE command.
|
|
by disabling newly introduced memory protection by default and adding a CLI switch (/protectMemory) to enable it when needed. This fixes issue https://github.com/veracrypt/VeraCrypt/issues/536
|
|
line in Format and Expander
|
|
created on disk or partition.
|
|
|
|
on Ubuntu 14.04, 12.04 and Debian 8
|
|
on GTK
|
|
* Revert "Linux: Fix failure to run VeraCrypt binary built for console mode on headless machines (fix issue https://github.com/veracrypt/VeraCrypt/issues/531)"
The build failure still exists for system wxGTK compiled with '--disable-gui':
```
In file included from TextUserInterface.cpp:27:
TextUserInterface.h: In member function ‘virtual bool VeraCrypt::TextUserInterface::Initialize(int&, wxChar**)’:
TextUserInterface.h:50:63: error: ‘wxAppBase’ has not been declared
50 | virtual bool Initialize (int &argc, wxChar **argv) { return wxAppBase::Initialize(argc, argv); }
```
This reverts commit 737e1f126b8826ed02418266e590e195aebdd7c0.
* Revert "Linux: fix compilation error when building console-only version of VeraCrypt that is statically linked to wxWidgets"
The build failure still exists for system wxGTK compiled with '--disable-gui':
```
In file included from TextUserInterface.cpp:27:
TextUserInterface.h: In member function ‘virtual bool VeraCrypt::TextUserInterface::Initialize(int&, wxChar**)’:
TextUserInterface.h:50:63: error: ‘wxAppBase’ has not been declared
50 | virtual bool Initialize (int &argc, wxChar **argv) { return wxAppBase::Initialize(argc, argv); }
```
This reverts commit 14bee5e6a227701e78c5fec04064c0494f6361f0.
* src/Main/Main.make: simplify the WX_CONFIG_LIBS logic
Irrespective of whether we are linking against widgets statically or
dynamically, pull in only 'base' when GUI is disabled, and
'adv,core,base' when GUI is enabled. When GUI is disabled, the C/CXX
flag must include '-DwxUSE_GUI=0' for this to work.
* src/Makefile: pass '-DwxUSE_GUI=0' when NOGUI=1
veracrypt with NOGUI=1 fails to properly link against wxGTK compiled
with '--disable-gui' only using the 'base' library because the wx's
setup.h implicitly defines wxUSE_GUI=1, which then changes the
definition of various structures, requiring symbols from the core
library as well.
For example, wxwidgets include/wx/app.h defines:
#if wxUSE_GUI
class WXDLLIMPEXP_CORE wxAppBase : public wxAppConsole
...
[snip]
...
#else // !GUI
// wxApp is defined in core and we cannot define another one in wxBase,
// so use the preprocessor to allow using wxApp in console programs too
#define wxApp wxAppConsole
#endif // GUI/!GUI
To fix this, pass '-DwxUSE_GUI=0' when compiling veracrypt with
NOGUI=1.
Closes: https://github.com/veracrypt/VeraCrypt/issues/531
|
|
using wxWidgets 3.1.3
|
|
|
|
|
|
(https://github.com/veracrypt/VeraCrypt/issues/9#issuecomment-565833478)
|
|
creation of file containers
|
|
so that it can still be moved by user using mouse (https://github.com/veracrypt/VeraCrypt/issues/546)
|
|
as a way to workaround for situations where UI is not visible or can't be move (for example, when changing display monitor with a different resolution).
|
|
method that takes a size_t argument (we cast to uint32)
|
|
container with .tc extension
|
|
reflecting the value of /noisocheck switch when specified in VeraCrypt Format command line.
|
|
that is statically linked to wxWidgets
|
|
|
|
|
|
|
|
creation of large file container if quick format is selected. This switch comes with security issues since it will embed existing content on disk into the file container which may expose sensitive content to an attacker who has access to the file container.
|
|
reader disk by chunks of at most 64 KiB. Fix https://github.com/veracrypt/VeraCrypt/issues/562.
|
|
|
|
that come with the following modifications: - Fix F5 showing previous password after failed authentication attempt. Ensure that even wrong password value are cleared from memory.
|
|
to Windows.
|
|
|
|
Signed-off-by: alt3r 3go <alt3r.3go@protonmail.com>
|
|
make sens under XP.
|
|
especially for keyfiles.
|
|
|
|
CoreUnix::MountVolume (#565)
|
|
to allow calling functions needed for CVE-2019-19501 fix while still protecting against memory access by non-admin processes.
|
|
|
|
execution of VeraCrypt Expander (CVE-2019-19501)
|
|
|
|
Signed-off-by: alt3r 3go <alt3r.3go@protonmail.com>
|
|
modifying it through UI
|
|
VeraCrypt as first bootloader of the system if the current first bootloader is Windows one.
|
|
different from us or different from Microsoft one.
|
|
updating of EFI BIOS boot menu on shutdown. This will help better manage multi-boot scenarios where we should not mess up with boot order (e.g. grub2 case)
|
|
that come with the following modifications: - Fix "ActionFailed" not working and add "ActionCancelled" to customize handling of user hitting ESC on password prompt
|
|
headless machines (fix issue https://github.com/veracrypt/VeraCrypt/issues/531)
|
|
|
|
|
|
if changing the keyboard layout failed (#539)
When my system broke and I had to use WindowsPE to rescue some files the password dialog always closed immediately. There was no chance to mount the system device using the GUI. It took me a while to realize that I could try using the CLI by passing the password as a parameter (which might not be so obvious for not advanced users).
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
|
|