| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
windows
|
|
architecture.
|
|
for all modules to protect against simple binaries tampering.
|
|
administrative privileges for extraction.
|
|
upgrade.
|
|
|
|
|
|
installation directory.
|
|
upgrading.
|
|
|
|
|
|
|
|
|
|
|
|
Windows 64-bit. Implement deleting locked files after machine reboot.
|
|
tool Coverity.
|
|
|
|
arbitrary code execution with elevation of privilege (CVE-2016-1281)
|
|
cases.
|
|
|
|
software.
|
|
installation. Avoid using driver handle to check if we are using system encryption.
|
|
|
|
64-bit executable binaries.
|
|
1.0f-2 (solve Windows 10 issue) . Remove extra VeraCrypt files that may remain after uninstalling it.
|
|
and TrueCrypt 3.0.
|
|
System32 since now all binaries are native 64-bit on 64-bit machines.
|
|
reported by users
|
|
previously.
|
|
VeraCrypt driver file.
|
|
install 64-bit exe files on Windows 64-bit. This gives a boot in performance for encryption/decryption of partitions/drives on Windows 64-bit.
|
|
and checking memory allocation.
|
|
program instead of uninstall directly in order to avoid being flagged as legacy application by the Windows Program Compatibility Assistant (see number 5 in Microsoft UI Design Standard https://msdn.microsoft.com/en-us/library/ms954377.aspx)
|
|
|
|
|
|
VeraCrypt COM interfaces that were left after upgrading.
|
|
|
|
|
|
more checks. Add extra checks. Solve various issues.
|
|
during uninstall.
|
|
became important after the introduction of the wait dialog in order to avoid having message boxes behind the wait dialog.
|
|
donation link.
|
|
the same version detected.
|
|
potential security issues.
|
|
inherited from version 0x71a
|
|
|
|
hijacked (Microsoft Security Advisory 2269637).
|
|
Resources::GetTrueCryptIcon to Resources::GetVeraCryptIcon.
|
|
|
|
|
