Age | Commit message (Collapse) | Author | Files | Lines |
|
Windows Vista,7, 8 and 8.1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
equivalents
This fixed failure to build driver for ARM64 with latest VS 2019
|
|
|
|
System encryption still not implemented on ARM64
|
|
when creating hidden volumes in direct mode inside them
|
|
|
|
|
|
Format.exe"/"VeraCrypt.exe" on a 64-bit machine where VeraCrypt is already installed
|
|
|
|
|
|
to be created in Format wizard
|
|
|
|
or volume creation and propose to disable it
|
|
creation of Hidden volume or resuming non-system in-place encryption
|
|
(e.g. KeePass) which is more secure than using clipboard.
|
|
|
|
|
|
|
|
|
|
keyfiles as Outer volume
|
|
|
|
|
|
command line
|
|
|
|
|
|
|
|
|
|
that was causing volume headers to be corrupted.
|
|
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
|
|
|
|
(https://github.com/veracrypt/VeraCrypt/issues/9#issuecomment-565833478)
|
|
creation of file containers
|
|
reflecting the value of /noisocheck switch when specified in VeraCrypt Format command line.
|
|
|
|
|
|
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.
|
|
especially for keyfiles.
|
|
|
|
|
|
|
|
|
|
|
|
container creation
|