Age | Commit message (Collapse) | Author | Files | Lines |
|
constructor to _TEXT_EDIT_DIALOG_PARAM and = operator to HostDevice
|
|
SSE2 instructions _mm_load_si128. Now we use _mm_loadu_si128 instead which is not slower than _mm_load_si128 on recent CPUs
|
|
|
|
keyfiles as Outer volume
|
|
volume creation wizard
|
|
|
|
volumes passwords
|
|
volume
|
|
when probing disk real size
|
|
fail gracefully
|
|
|
|
supported by CPU that caused the free space of newly created volumes not filled with random data even if "quick format" is not selected by user.
|
|
enabled in order to be follow the same execution path as the result of benchmark calculations.
|
|
has returned random bytes successfully at least once during the lifetime of RandomNumberGenerator
|
|
done for Windows previously
|
|
encryption is enabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in the language selection dialog and then select English followed by OK.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
command line
|
|
always cleared from RAM when VeraCrypt exits
|
|
|
|
|
|
issues caused by previous implementation
|
|
|
|
|
|
* Adding Processor Groups support for more than 64 processors
* Revert " Adding Processor Groups support for more than 64 processors"
This reverts commit e1d5fe0a55f46a53549450972c5b5506a43ca94c.
* Adding Processor Groups support for >64 logical processors
|
|
configuration
|
|
will not add any benefit compared to standard ShellExecute while at the same time potentially causing issue when opening links.
|
|
|
|
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.
|
|
|