Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
encryption can be inferred from VeraCrypt bootloader only in the case of MBR boot mode.
|
|
|
|
|
|
|
|
latest changes. Indicate that MSI requires Windows 10 or newer.
|
|
|
|
|
|
|
|
|
|
Mountain Lion
|
|
macOS Big Sur.
|
|
* *: source files should not be executable
* *: make sure files have final newline
* *: remove BOM from text files
* translations: unify headers
* *: fix typos
* *: trim excess whitespace
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"My Volume" for file container name in order to avoid confusion about nature of file nature for beginners who expect a file to always have an extension (cf https://github.com/veracrypt/VeraCrypt/issues/663) Update screenshots to reflect changes in VeraCrypt UI
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(/keyfile, /tokenlib, /tokenpin and /secureDesktop)
|
|
|
|
|
|
|
|
CLI switches
|
|
|
|
in EFI mode we can't encrypt whole disk
|
|
|
|
VeraCrypt Format.
|
|
|
|
|
|
|
|
Rescue Disk and not only MBR legacy one.
|