macOS: Fix packaging error due to template dmg being too small.

To fix it, we resized the template dmg using hdiutil resize --size 16M

.gitattributes

@@ -0,0 +1,51 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+*	text=auto
+
+# Explicitly declare text files that could be normalized and converted
+# to native line endings on checkout. However, as per the policy they're
+# supposed to have LF endings on all platforms.
+*.[ch]	text diff=cpp eol=lf
+*.[ch]pp	text diff=cpp eol=lf
+*.asm	text eol=lf
+Makefile	text eol=lf
+*.make	text eol=lf
+*.mk	text eol=lf
+*.inc	text eol=lf
+*.md	text eol=lf
+*.xml	text eol=lf
+*.xpm	text -diff -merge eol=lf
+*.pem	text -diff -merge eol=lf
+*.cer	text -diff -merge eol=lf
+*.manifest	text eol=lf
+*.sh	text eol=lf
+*.txt	text eol=lf
+*.html	text diff=html eol=lf
+*.idl	text eol=lf
+*.fbp	text eol=lf
+*.rgs	text eol=lf
+*.pkgproj	text eol=lf
+*.S	text eol=lf
+Sources	text eol=lf
+
+# Declare files that will always have LF line endings on checkout.
+*.desktop	text eol=lf
+
+# Declare files that will always have CRLF line endings on checkout.
+*.sln	text eol=crlf
+*.vcproj	text eol=crlf
+*.rc	text eol=crlf
+*.bat	text eol=crlf
+*.cmd	text eol=crlf
+
+# Denote all files that are truly binary and should not be modified.
+*.png	binary
+*.jpg	binary
+*.pdf	binary
+*.bmp	binary
+*.ico	binary
+*.od[fgpst]	binary
+*.hc	binary
+*.icns	binary
+*.rtf	binary
+*.bz2	binary
+*.pfx	binary

.github/FUNDING.yml

@@ -0,0 +1 @@
+custom: "https://www.veracrypt.fr/en/Donation.html"

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,34 @@
+---
+name: Bug Report
+about: Found a bug? Let us know! 🐛
+labels: bug, unreviewed
+
+---
+
+<!-- Please provide a general summary of the issue in the title above. -->
+
+# Expected behavior
+<!-- Describe here what you have expected to happen -->
+
+# Observed behavior
+<!-- Describe here what happened instead of the expected behavior -->
+
+# Steps to reproduce
+<!-- Tell use all the steps you did so we can reproduce the problem -->
+1. 
+2. 
+3. 
+4.
+
+# Screenshots
+<!-- Add additional screenshots -->
+
+# Your Environment
+
+Please tell us more about your environment
+
+**VeraCrypt version:** <!-- f.e. 1.24-Update7 -->
+
+**Operating system and version:** <!-- f.e. Windows 10 build 19042 -->
+
+**System type:** <!-- f.e. 64-bit -->

.github/ISSUE_TEMPLATE/change.md

@@ -0,0 +1,30 @@
+---
+name: Change
+about: Change or extend functionality that already exists.
+labels: change, unreviewed
+
+---
+
+<!-- Please provide a general summary of your change in the title above. -->
+
+# Current behavior
+<!-- Describe here how it actually works -->
+
+# Desired behavior
+<!-- Describe here the difference from current behavior-->
+
+# Screenshots/Mockup/Designs
+<!-- Add additional screenshots, mockups or design proposals -->
+
+# Additional information
+<!-- Are there any additional requirements? Further ideas, ... -->
+
+# Your Environment
+
+Please tell us more about your environment
+
+**VeraCrypt version:** <!-- f.e. 1.24-Update7 -->
+
+**Operating system and version:** <!-- f.e. Windows 10 build 19042 -->
+
+**System type:** <!-- f.e. 64-bit -->

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,27 @@
+---
+name: Feature
+about: Add new functionality or suggest an idea to the project.
+labels: feature, unreviewed
+
+---
+
+<!-- Please provide a general summary of your feature in the title above. -->
+
+# Desired behavior
+<!-- Describe here what and why your feature should be added -->
+
+# Screenshots/Mockup/Designs
+<!-- Add additional screenshots, mockups or design proposals -->
+
+# Additional information
+<!-- Are there any additional requirements? Further ideas, ... -->
+
+# Your Environment
+
+Please tell us more about your environment
+
+**VeraCrypt version:** <!-- f.e. 1.24-Update7 -->
+
+**Operating system and version:** <!-- f.e. Windows 10 build 19042 -->
+
+**System type:** <!-- f.e. 64-bit -->

.github/stale.yml

@@ -0,0 +1,25 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 60
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because it has not had
+  recent activity. This probably means that it is not reproducible
+  or it has been fixed in a newer version. If it’s an enhancement
+  and hasn't been taken on for so long, then it seems no one has
+  the time to implement this.
+  Please reopen if you still encounter this issue with the [latest stable version](https://www.veracrypt.fr/en/Downloads.html).
+  You can also contribute directly by providing a pull request.
+  Thank you!

.github/workflows/build-linux.yml

@@ -0,0 +1,213 @@
+name: Build and test Linux
+
+on:
+  push:
+    branches: [ "master" ]
+    paths:
+      - 'src/Build/Include/Makefile.inc'
+      - 'src/Build/CMakeLists.txt'
+      - 'src/Build/build_cmake_deb.sh'
+      - 'src/Common/*.h'
+      - 'src/Common/*.cpp'
+      - 'src/Common/*.c'
+      - 'src/Core/**'
+      - 'src/Crypto/**'
+      - 'src/Driver/Fuse/**'
+      - 'src/Main/**'
+      - 'src/PKCS11/**'
+      - 'src/Platform/**'
+      - 'src/Resources/**'
+      - 'src/Setup/Linux/**'
+      - 'src/Volume/**'
+      - 'src/Makefile'
+      - '.github/workflows/build-linux.yml'
+  pull_request:
+    branches: [ "master" ]
+    paths:
+      - 'src/Build/Include/Makefile.inc'
+      - 'src/Build/CMakeLists.txt'
+      - 'src/Build/build_cmake_deb.sh'
+      - 'src/Common/*.h'
+      - 'src/Common/*.cpp'
+      - 'src/Common/*.c'
+      - 'src/Core/**'
+      - 'src/Crypto/**'
+      - 'src/Driver/Fuse/**'
+      - 'src/Main/**'
+      - 'src/PKCS11/**'
+      - 'src/Platform/**'
+      - 'src/Resources/**'
+      - 'src/Setup/Linux/**'
+      - 'src/Volume/**'
+      - 'src/Makefile'
+      - '.github/workflows/build-linux.yml'
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+env:
+  WXWIDGETS_VERSION: 3.2.5
+
+jobs:
+  ubuntu-build:
+
+    runs-on: ubuntu-22.04
+    timeout-minutes: 30
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Generate cache key
+      id: cache-key
+      run: |
+        echo "cache_key=$(echo ${{ env.WXWIDGETS_VERSION }}-$(sha256sum src/Makefile .github/workflows/build-linux.yml | awk '{print $1}'))" >> $GITHUB_OUTPUT
+
+    - name: Cache wxBuildConsole
+      uses: actions/cache@v3
+      id: cache-wxbuildconsole
+      with:
+        path: /tmp/wxBuildConsole
+        key: wxBuildConsole-${{ steps.cache-key.outputs.cache_key }}
+
+    - name: Cache wxBuildGUI
+      uses: actions/cache@v3
+      id: cache-wxbuildgui
+      with:
+        path: /tmp/wxBuildGUI
+        key: wxBuildGUI-${{ steps.cache-key.outputs.cache_key }}
+
+    - name: Cache wxWidgets
+      uses: actions/cache@v3
+      id: cache-wxwidgets
+      with:
+        path: /tmp/wxWidgets-${{ env.WXWIDGETS_VERSION }}
+        key: wxWidgets-${{ steps.cache-key.outputs.cache_key }}
+
+    - name: Install dependencies
+      run: sudo apt-get update && sudo apt-get install -y wget tar libpcsclite-dev libfuse-dev yasm libgtk-3-dev libayatana-appindicator3-dev cmake debhelper
+
+    - name: Download and extract wxWidgets to /tmp if build folders are missing
+      if: steps.cache-wxbuildconsole.outputs.cache-hit != 'true' || steps.cache-wxbuildgui.outputs.cache-hit != 'true' || steps.cache-wxwidgets.outputs.cache-hit != 'true'
+      run: |
+        wget https://github.com/wxWidgets/wxWidgets/releases/download/v${{ env.WXWIDGETS_VERSION }}/wxWidgets-${{ env.WXWIDGETS_VERSION }}.tar.bz2 -O /tmp/wxWidgets-${{ env.WXWIDGETS_VERSION }}.tar.bz2
+        mkdir -p /tmp/wxWidgets-${{ env.WXWIDGETS_VERSION }}
+        tar -xjf /tmp/wxWidgets-${{ env.WXWIDGETS_VERSION }}.tar.bz2 -C /tmp/wxWidgets-${{ env.WXWIDGETS_VERSION }} --strip-components=1
+
+    - name: Build VeraCrypt .deb packages
+      run: |
+        chmod +x src/Build/build_cmake_deb.sh
+        src/Build/build_cmake_deb.sh WXSTATIC INDICATOR
+
+    - name: Upload GUI .deb packages
+      uses: actions/upload-artifact@v3
+      with:
+        name: veracrypt-gui-debs
+        path: /tmp/VeraCrypt_Packaging/GUI/Packaging/veracrypt-*.*
+
+    - name: Upload Console .deb packages
+      uses: actions/upload-artifact@v3
+      with:
+        name: veracrypt-console-debs
+        path: /tmp/VeraCrypt_Packaging/Console/Packaging/veracrypt-console-*.*
+
+    - name: Install and test VeraCrypt GUI .deb packages
+      run: |
+        sudo apt install -y /tmp/VeraCrypt_Packaging/GUI/Packaging/veracrypt-*.deb
+        veracrypt --text --test && veracrypt --text --version
+        sudo veracrypt --text --non-interactive Tests/test.sha256.hc --hash sha256 --slot 1 --password test --mount-options=ro
+        sudo veracrypt --text --non-interactive Tests/test.sha512.hc --hash sha512 --slot 2 --password test --mount-options=ro
+        sudo veracrypt --text --non-interactive Tests/test.streebog.hc --hash streebog --slot 3 --password test --mount-options=ro
+        sudo veracrypt --text --non-interactive Tests/test.whirlpool.hc --hash whirlpool --slot 4 --password test --mount-options=ro
+        sudo veracrypt --text --list
+        echo -n "Dummy" > /tmp/expected_content.txt
+        if cmp -s /media/veracrypt1/Dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.sha256.hc is valid."
+        else
+          echo "Content of test.sha256.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt2/Dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.sha512.hc is valid."
+        else
+          echo "Content of test.sha512.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt3/Dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.streebog.hc is valid."
+        else
+          echo "Content of test.streebog.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt4/Dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.whirlpool.hc is valid."
+        else
+          echo "Content of test.whirlpool.hc is invalid!"
+          exit 1
+        fi
+        sudo veracrypt -d
+        sudo apt remove -y veracrypt
+
+    - name: Install and test VeraCrypt Console .deb packages
+      run: |
+        sudo apt install -y /tmp/VeraCrypt_Packaging/Console/Packaging/veracrypt-console-*.deb
+        veracrypt --test && veracrypt --version
+        sudo veracrypt --non-interactive Tests/test.sha256.hc --hash sha256 --slot 1 --password test --mount-options=ro
+        sudo veracrypt --non-interactive Tests/test.sha512.hc --hash sha512 --slot 2 --password test --mount-options=ro
+        sudo veracrypt --non-interactive Tests/test.streebog.hc --hash streebog --slot 3 --password test --mount-options=ro
+        sudo veracrypt --non-interactive Tests/test.whirlpool.hc --hash whirlpool --slot 4 --password test --mount-options=ro
+        sudo veracrypt --list
+        echo -n "Dummy" > /tmp/expected_content.txt
+        if cmp -s /media/veracrypt1/dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.sha256.hc is valid."
+        else
+          echo "Content of test.sha256.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt2/dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.sha512.hc is valid."
+        else
+          echo "Content of test.sha512.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt3/dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.streebog.hc is valid."
+        else
+          echo "Content of test.streebog.hc is invalid!"
+          exit 1
+        fi
+        if cmp -s /media/veracrypt4/dummy.txt /tmp/expected_content.txt; then
+          echo "Content of test.whirlpool.hc is valid."
+        else
+          echo "Content of test.whirlpool.hc is invalid!"
+          exit 1
+        fi
+        sudo veracrypt -d
+        sudo apt remove -y veracrypt-console
+
+    - name: Cleanup old caches
+      uses: actions/github-script@v6
+      if: always()
+      with:
+        github-token: ${{ secrets.GITHUB_TOKEN }}
+        script: |
+          const caches = await github.rest.actions.getActionsCacheList({
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+          })
+          for (const cache of caches.data.actions_caches) {
+            if (cache.key.startsWith('wxBuildConsole-') || cache.key.startsWith('wxBuildGUI-') || cache.key.startsWith('wxWidgets-')) {
+              if (cache.key !== `wxBuildConsole-${{ steps.cache-key.outputs.cache_key }}` &&
+                  cache.key !== `wxBuildGUI-${{ steps.cache-key.outputs.cache_key }}` &&
+                  cache.key !== `wxWidgets-${{ steps.cache-key.outputs.cache_key }}`) {
+                console.log(`Deleting cache with key: ${cache.key}`)
+                await github.rest.actions.deleteActionsCacheById({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  cache_id: cache.id,
+                })
+              }
+            }
+          }
+

.github/workflows/xmlvalidate.sh

@@ -0,0 +1,42 @@
+#!/bin/bash
+fail=false
+
+# Get all string keys
+KEYS=$(grep -oP '<entry[\ ]+lang="[^"]+"[\ ]+key="\K[^"]+' "$1"/src/Common/Language.xml)
+
+for file in {"$1"/Translations/Language.*.xml,"$1"/src/Common/Language.xml}; do
+  echo "$file"
+  passes=true
+  
+  # Validate xml
+  output=$(fxparser -V "$file")
+  returnvalue=$?
+
+  if [ "$returnvalue" -ne "0" ]; then
+    passes=false
+    fail=true
+    echo $output
+  fi
+
+  # Ensure each key found in common xml is found in translation xmls
+  for key in $KEYS; do
+    if ! grep -q "$key" "$file"; then
+      echo "Key $key not found in $file"
+      passes=false
+      fail=true
+    fi
+  done
+  
+  if [ "$passes" = true ]; then
+    echo -e "\e[32m$file passes xml validation.\e[0m"
+  else
+    echo -e "\e[31m$file fails xml validation.\e[0m"
+  fi
+  
+done
+
+if [ "$fail" = true ]; then
+  exit 1
+else
+  exit 0
+fi

.github/workflows/xmlvalidate.yml

@@ -0,0 +1,36 @@
+name: Validate XML
+
+on:
+  push:
+    branches: [ "ci" ]
+    paths:
+      - 'Translations/*'
+      - 'src/Common/Language.xml'
+      - '.github/workflows/xmlvalidate.*'
+  pull_request:
+    branches: [ "ci" ]
+    paths:
+      - 'Translations/*'
+      - 'src/Common/Language.xml'
+      - '.github/workflows/xmlvalidate.*'
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  validate:
+
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Setup Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: 'latest'
+    - name: Install fast-xml-parser
+      run: npm install fast-xml-parser -g
+    - name: Run XML validator script
+      run: ${{ github.workspace }}/.github/workflows/xmlvalidate.sh "${{ github.workspace }}"

.gitignore

@@ -0,0 +1,112 @@
+# For those using Visual Studio Code for development
+.vscode/
+
+# CLion
+.idea/
+
+# VC Linux build artifacts
+*.o
+*.o0
+*.d
+*.a
+*.bmp.h
+*.xml.h
+*.txt.h
+*.h.gch
+src/Main/veracrypt
+*.osse41
+*.ossse3
+*.oshani
+*.oarmv8crypto
+
+# VC macOS build artifacts
+src/Main/VeraCrypt
+src/Main/VeraCrypt.app
+src/Main/*.dmg
+src/Setup/MacOSX/*.pkg
+*.oo
+*.o.32
+*.o.64
+.DS_Store
+
+# wxWidgets Linux build artifacts
+src/wxrelease
+src/wxdebug
+
+src/.vs
+
+src/Boot/Windows/obj
+src/Boot/Windows/Release
+src/Boot/Windows/Release_AES
+src/Boot/Windows/Release_AES_SHA2
+src/Boot/Windows/Release_Camellia
+src/Boot/Windows/Release_Camellia_SHA2
+src/Boot/Windows/Release_Serpent
+src/Boot/Windows/Release_Serpent_SHA2
+src/Boot/Windows/Release_SHA2
+src/Boot/Windows/Release_Twofish
+src/Boot/Windows/Release_Twofish_SHA2
+src/Boot/Windows/Rescue
+src/Boot/Windows/Rescue_AES
+src/Boot/Windows/Rescue_AES_SHA2
+src/Boot/Windows/Rescue_Camellia
+src/Boot/Windows/Rescue_Camellia_SHA2
+src/Boot/Windows/Rescue_Serpent
+src/Boot/Windows/Rescue_Serpent_SHA2
+src/Boot/Windows/Rescue_SHA2
+src/Boot/Windows/Rescue_Twofish
+src/Boot/Windows/Rescue_Twofish_SHA2
+
+src/Common/Debug
+src/Common/obj_driver_debug
+src/Common/obj_driver_release
+src/Common/Release
+src/Common/x64
+src/Common/ARM64
+src/Common/*.log
+
+src/Crypto/Debug
+src/Crypto/obj_driver_debug
+src/Crypto/obj_driver_release
+src/Crypto/Release
+src/Crypto/x64
+src/Crypto/ARM64
+
+src/Debug
+
+src/Driver/Debug
+src/Driver/obj
+src/Driver/obj_driver_debug
+src/Driver/obj_driver_release
+src/Driver/Release
+src/Driver/ARM64
+
+src/ExpandVolume/Debug
+src/ExpandVolume/Release
+src/ExpandVolume/x64
+src/ExpandVolume/ARM64
+src/ExpandVolume/*.tlb
+
+src/Format/Debug
+src/Format/Release
+src/Format/x64
+src/Format/ARM64
+src/Format/*.tlb
+src/Format/FormatCom_h.h
+src/Format/FormatCom_i.c
+
+src/Mount/Debug
+src/Mount/Release
+src/Mount/x64
+src/Mount/ARM64
+src/Mount/*.tlb
+src/Mount/MainCom_h.h
+src/Mount/MainCom_i.c
+
+src/Setup/Debug
+src/Setup/PortableDebug
+src/Setup/Release
+src/Setup/PortableRelease
+
+src/SetupDLL/Debug
+src/SetupDLL/Release

README.md

@@ -1,9 +1,7 @@
 This archive contains the source code of VeraCrypt.
-It is based on original TrueCrypt 7.1a with security enhancements and modifications.
+It is based on the original TrueCrypt 7.1a with security enhancements and modifications.
 
-
-Important
-=========
+# Important
 
 You may use the source code contained in this archive only if you accept and
 agree to the license terms contained in the file 'License.txt', which is
@@ -12,246 +10,226 @@ included in this archive.
 Note that the license specifies, for example, that a derived work must not be
 called 'TrueCrypt' or 'VeraCrypt'
 
+# Contents
 
+[I. Windows](#i-windows)
 
-Contents
-========
+[II. Linux and Mac OS X](#ii-linux-and-mac-os-x)
 
-I. Windows
-	Requirements for Building VeraCrypt for Windows
-	Instructions for Building VeraCrypt for Windows
-	Instructions for Signing and Packaging VeraCrypt for Windows
+[III. FreeBSD](#iii-freebsd)
 
-II. Linux and Mac OS X
-	Requirements for Building VeraCrypt for Linux and Mac OS X
-	Instructions for Building VeraCrypt for Linux and Mac OS X
-	Mac OS X specifics
-	
-III. FreeBSD and OpenSolaris
+[IV. Third-Party Developers (Contributors)](#iv-third-party-developers-contributors)
 
-IV. Third-Party Developers (Contributors)
+[V. Legal Information](#v-legal-information)
 
-V. Legal Information
+[VI. Further Information](#vi-further-information)
 
-VI. Further Information
+# I. Windows
 
+## Requirements for Building VeraCrypt for Windows:
 
-
-I. Windows
-==========
-
-Requirements for Building VeraCrypt for Windows:
-------------------------------------------------
-
-- Microsoft Visual C++ 2008 SP1 (Professional Edition or compatible)
-- Microsoft Visual C++ 1.52 (available from MSDN Subscriber Downloads)
-- Microsoft Windows SDK for Windows 7 (configured for Visual C++)
-- Microsoft Windows Driver Kit 7.1.0 (build 7600.16385.1)
-- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
-  header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20)
-- NASM assembler 2.08 or compatible
-- gzip compressor
+A detailed guide on how to build VeraCrypt on Windows can be found in
+the [documentation](./doc/html/CompilingGuidelineWin.html) in the repository and
+it is also available [online](https://www.veracrypt.fr/en/CompilingGuidelineWin.html).
 
 IMPORTANT:
 
 The 64-bit editions of Windows Vista and later versions of Windows, and in
-some cases (e.g. playback of HD DVD content) also the 32-bit editions, do not
+some cases (e.g. playback of HD DVD content) also the 32-bit editions do not
 allow the VeraCrypt driver to run without an appropriate digital signature.
 Therefore, all .sys files in official VeraCrypt binary packages are digitally
-signed with the digital certificate of the IDRIX, which was
-issued by Thawt certification authority. At the end of each official .exe and
+signed with the digital certificate of the IDRIX, which was issued by
+GlobalSign certification authority. At the end of each official .exe and
 .sys file, there are embedded digital signatures and all related certificates
 (i.e. all certificates in the relevant certification chain, such as the
 certification authority certificates, CA-MS cross-certificate, and the
-IDRIX certificate). Keep this in mind if you compile VeraCrypt
-and compare your binaries with the official binaries. If your binaries are
-unsigned, the sizes of the official binaries will usually be approximately
-10 KB greater than sizes of your binaries (there may be further differences
-if you use a different version of the compiler, or if you install a different
-or no service pack for Visual Studio, or different hotfixes for it, or if you
-use different versions of the required SDKs).
+IDRIX certificate).
 
+Keep this in mind if you compile VeraCrypt and compare your binaries with the
+official binaries. If your binaries are unsigned, the sizes of the official
+binaries will usually be approximately 10 KiB greater than the sizes of your
+binaries (there may be further differences if you use a different version of
+the compiler, or if you install a different or no service pack for Visual
+Studio, or different hotfixes for it, or if you use different versions of
+the required SDKs).
 
-Instructions for Building VeraCrypt for Windows:
-------------------------------------------------
+## Instructions for Signing and Packaging VeraCrypt for Windows:
 
-1) Create an environment variable 'MSVC16_ROOT' pointing to the folder 'MSVC15'
-   extracted from the Visual C++ 1.52 self-extracting package.
+First, create an environment variable 'WSDK81' pointing to the Windows SDK
+for Windows 8.1 installation directory.
 
-   Note: The 16-bit installer MSVC15\SETUP.EXE cannot be run on 64-bit Windows,
-   but it is actually not necessary to run it. You only need to extract the
-   folder 'MSVC15', which contains the 32-bit binaries required to build the
-   VeraCrypt Boot Loader.
+The folder "Signing" contains a batch file (sign.bat) that will sign all
+VeraCrypt components using a code signing certificate present on the
+certificate store and build the final installation setup and MSI package.
+The batch file assumes that the code signing certificate is issued by
+GlobalSign. This is the case for IDRIX's certificate. If yours is issued by
+another CA, then you should put its intermediate certificates in the "Signing"
+folder and modify sign.bat accordingly.
 
-2) If you have installed the Windows Driver Development Kit in another
-   directory than '%SYSTEMDRIVE%\WinDDK', create an environment variable
-   'WINDDK_ROOT' pointing to the DDK installation directory.
+To generate MSI packages, WiX Toolset v3.11 must be installed.
 
-3) Copy the PKCS #11 header files to a standard include path or create an
-   environment variable 'PKCS11_INC' pointing to the directory where
-   the PKCS #11 header files are installed.
+## VeraCrypt EFI Boot Loader:
 
-4) Open the solution file 'VeraCrypt.sln' in Microsoft Visual Studio 2008.
+VeraCrypt source code contains pre-built EFI binaries under src\Boot\EFI.
+The source code of VeraCrypt EFI Boot Loader is licensed under LGPL and
+it is available at https://github.com/veracrypt/VeraCrypt-DCS.
+For build instructions, please refer to the file src\Boot\EFI\Readme.txt.
 
-5) Select 'All' as the active solution configuration.
+# II. Linux and Mac OS X
 
-6) Build the solution.
+A detailed guide on how to build VeraCrypt on Linux can be found in
+the [documentation](./doc/html/CompilingGuidelineLinux.html) in the repository and
+it is also available [online](https://www.veracrypt.fr/en/CompilingGuidelineLinux.html).
 
-7) If successful, there should be newly built VeraCrypt binaries in the
-   'Release' folder.
-
-Instructions for Signing VeraCrypt for Windows:
-------------------------------------------------
-
-The folder "Signing" contains a batch file (sign.bat) that will sign all 
-VeraCrypt components using a code signing certificate present on the 
-certificate store and also build the final installation setup.
-The batch file suppose that the code signing certificate is issued by Thawt.
-This is the case for IDRIX's certificate. If yours is issued by another CA, 
-then you should put the Root and Intermediate certificates in the "Signing" 
-folder and then modify sign.bat accordingly.
-
-
-II. Linux and Mac OS X
-======================
-
-Requirements for Building VeraCrypt for Linux and Mac OS X:
------------------------------------------------------------
+## Requirements for Building VeraCrypt for Linux and Mac OS X:
 
 - GNU Make
 - GNU C++ Compiler 4.0 or compatible
-- Apple Xcode (Mac OS X only)
-- NASM assembler 2.08 or compatible (x86/x64 architecture only)
+- Apple Xcode or Xcode command line tools (Mac OS X only)
+- YASM 1.3.0 or newer (Linux only, x86/x64 architecture only)
 - pkg-config
 - wxWidgets 3.0 shared library and header files installed or
-  wxWidgets 3.0 library source code (available at http://www.wxwidgets.org)
-- FUSE library and header files (available at http://fuse.sourceforge.net
+  wxWidgets 3.0 library source code (available at https://www.wxwidgets.org)
+- FUSE library and header files (available at https://github.com/libfuse/libfuse
   and https://osxfuse.github.io/)
-- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
-  header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20).
-  They are already included in the source tree under the directory PKCS11 but 
-  it is possible to override it using the environment variable 'PKCS11_INC'. 
+- PCSC-lite library and header files (available at https://github.com/LudovicRousseau/PCSC)
 
+## Instructions for Building VeraCrypt for Linux and Mac OS X:
 
-Instructions for Building VeraCrypt for Linux and Mac OS X:
------------------------------------------------------------
+1. Change the current directory to the root of the VeraCrypt source code.
 
-1) Change the current directory to the root of the VeraCrypt source code.
-
-2) If you have no wxWidgets shared library installed, run the following
+2. If you have no wxWidgets shared library installed, run the following
    command to configure the wxWidgets static library for VeraCrypt and to
-   build it: 
+   build it:
 
-   $ make WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild
+   `$ make WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild`
 
-   The variable WX_ROOT must point to the location of the source code of the
+   The variable `WX_ROOT` must point to the location of the source code of the
    wxWidgets library. Output files will be placed in the './wxrelease/'
    directory.
 
-3) To build VeraCrypt, run the following command:
+3. To build VeraCrypt, run the following command:
 
-   $ make
+   `$ make`
 
    or if you have no wxWidgets shared library installed:
-   
-   $ make WXSTATIC=1
 
-4) If successful, the VeraCrypt executable should be located in the directory
+   `$ make WXSTATIC=1`
+
+4. If successful, the VeraCrypt executable should be located in the directory
    'Main'.
 
 By default, a universal executable supporting both graphical and text user
-interface is built. To build a console-only executable, which requires no GUI
-library, use the 'NOGUI' parameter:
+interface (through the switch --text) is built.
+On Linux, a console-only executable, which requires no GUI library, can be
+built using the 'NOGUI' parameter:
 
-   $ make NOGUI=1 WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild
-   $ make NOGUI=1 WXSTATIC=1
-   
+`$ make NOGUI=1 WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild`
 
-Mac OS X specifics:
------------------------------------------------------------
-   
-Under MacOSX, the SDK for OSX 10.7 is used by default. To use another version
-of the SDK (e.i. 10.6), you can export the environment variable VC_OSX_TARGET :
-	
-	$ export VC_OSX_TARGET=10.6
+`$ make NOGUI=1 WXSTATIC=1`
 
+On MacOSX, building a console-only executable is not supported.
 
-Before building under MacOSX, pkg-config must be installed if not yet available.
-Get it from http://pkgconfig.freedesktop.org/releases/pkg-config-0.28.tar.gz and
-compile using the following commands : 
+## Mac OS X specifics:
 
-	$ ./configure --with-internal-glib
-	$ make
-	$ sudo make install
+Under MacOSX, the latest installed SDK is used by default. To use a different version
+of the SDK when building using make, you can export the environment variable VC_OSX_SDK:
+
+`$ export VC_OSX_SDK=13.0`
+
+For development dependencies management, you can use [homebrew](https://brew.sh).
+
+`$ brew install pkg-config yasm wxwidgets`
+
+You also need system dependencies
+
+`$ brew install --cask macfuse packages`
+
+After installing dependencies via brew, you can build a local development build
+
+`$ ./src/Build/build_veracrypt_macosx.sh -b`
+
+If you want to build the package, you must pass `-p` to the build script above. The built
+executable will be in `.src/Main`
+
+If you prefer to build from sources, or without homebrew, pkg-config and packages must be installed.
+
+Get pkg-config from https://pkgconfig.freedesktop.org/releases/pkg-config-0.29.2.tar.gz and
+compile using the following commands:
+
+`$ CFLAGS="-Wno-int-conversion" CXXFLAGS="-Wno-int-conversion" ./configure --with-internal-glib`
+
+`$ make`
+
+`$ sudo make install`
 
 After making sure pkg-config is available, download and install OSXFuse from
-https://osxfuse.github.io/ (MacFUSE compatibility layer must selected)
+https://osxfuse.github.io/
 
-The script build_veracrypt_macosx.sh available under "src/Build" performs the 
+The [build_veracrypt_macosx.sh](./src/Build/build_veracrypt_macosx.sh) script performs the
 full build of VeraCrypt including the creation of the installer pkg. It expects
-to find the wxWidgets 3.0.2 sources at the same level as where you put 
-VeraCrypt sources (e.i. if "src" path is "/Users/joe/Projects/VeraCrypt/src" 
-then wxWidgets should be at "/Users/joe/Projects/wxWidgets-wxWidgets-3.0.2")
+to find the wxWidgets 3.2.5 sources at the same level as where you put
+VeraCrypt sources (i.e. if "src" path is "/Users/joe/Projects/VeraCrypt/src"
+then wxWidgets should be at "/Users/joe/Projects/wxWidgets-3.2.5")
 
-The build process uses Code Signing certificates whose ID is specified in
-src/Main/Main.make (lines 167 & 169). You'll have to modify these lines to put
-the ID of your Code Signing certificates or comment them if you don't have one.
+The make build process uses Code Signing certificates whose ID is specified in
+src/Main/Main.make (look for lines containing "Developer ID Application" and
+"Developer ID Installer"). You'll have to modify these lines to put the ID of
+your Code Signing certificates or comment them out if you don't have one.
 
 Because of incompatibility issues with OSXFUSE, the SDK 10.9 generates a
 VeraCrypt binary that has issues communicating with the OSXFUSE kernel extension.
-Thus, we recommend to use the SDK 10.8 or earlier for building VeraCrypt.
+Thus, we recommend using a different OSX SDK version for building VeraCrypt.
 
+The Packages installer that is used for the VeraCrypt official build has been notarized by IDRIX and it is available at
+https://github.com/idrassi/packages/releases
 
+# III. FreeBSD
 
-III. FreeBSD and OpenSolaris
-============================
+FreeBSD is supported starting from version 11.
+The build requirements and instructions are the same as Linux except that gmake
+should be used instead of make.
 
-FreeBSD and OpenSolaris are not yet supported.
-
-
-
-IV. Third-Party Developers (Contributors)
-=========================================
+# IV. Third-Party Developers (Contributors)
 
 If you intend to implement a feature, please contact us first to make sure:
 
-1) That the feature has not been implemented (we may have already implemented
+1. That the feature has not been implemented (we may have already implemented
    it, but haven't released the code yet).
-2) That the feature is acceptable.
-3) Whether we need help of third-party developers with implementing the feature.
+2. That the feature is acceptable.
+3. Whether we need the help of third-party developers with implementing the feature.
 
 Information on how to contact us can be found at:
-https://veracrypt.codeplex.com/
+https://www.veracrypt.fr/
 
+# V. Legal Information
 
+## Copyright Information
 
-V. Legal Information
-====================
+This software as a whole:  
+Copyright (c) 2013-2024 IDRIX. All rights reserved.  
 
-Copyright Information
----------------------
+Portions of this software:  
+Copyright (c) 2013-2024 IDRIX. All rights reserved.  
+Copyright (c) 2003-2012 TrueCrypt Developers Association. All rights reserved.  
+Copyright (c) 1998-2000 Paul Le Roux. All rights reserved.  
+Copyright (c) 1998-2008 Brian Gladman, Worcester, UK. All rights reserved.  
+Copyright (c) 1995-2023 Jean-loup Gailly and Mark Adler.  
+Copyright (c) 2016 Disk Cryptography Services for EFI (DCS), Alex Kolotnikov  
+Copyright (c) 1999-2023 Dieter Baron and Thomas Klausner.  
+Copyright (c) 2013, Alexey Degtyarev. All rights reserved.  
+Copyright (c) 1999-2016 Jack Lloyd. All rights reserved.  
+Copyright (c) 2013-2019 Stephan Mueller <smueller@chronox.de>  
+Copyright (c) 1999-2023 Igor Pavlov  
 
-This software as a whole:
-Copyright (c) 2013-2014 IDRIX. All rights reserved.
-
-Portions of this software:
-Copyright (c) 2003-2012 TrueCrypt Developers Association. All rights reserved.
-Copyright (c) 1998-2000 Paul Le Roux. All rights reserved.
-Copyright (c) 1998-2008 Brian Gladman, Worcester, UK. All rights reserved.
-Copyright (c) 2002-2004 Mark Adler. All rights reserved.
 For more information, please see the legal notices attached to parts of the
 source code.
 
-Trademark Information
----------------------
+## Trademark Information
 
-Any trademarks contained in the source code, binaries, and/or in the 
+Any trademarks contained in the source code, binaries, and/or in the
 documentation, are the sole property of their respective owners.
 
+# VI. Further Information
 
-
-VI. Further Information
-=======================
-
-http://www.veracrypt.fr
-
+https://www.veracrypt.fr

Tests/bench.bat

@@ -0,0 +1,140 @@
+@echo off
+setlocal EnableDelayedExpansion
+
+:: Define constants
+set "VERACRYPT_PATH=c:\Program Files\VeraCrypt\veracrypt.exe"
+set "PASSWORD=test"
+set "HIDDEN_PASSWORD=testhidden"
+
+:: Find a free drive letter
+call :freedrive mydriveletter || (
+    echo ERROR: No free drive letter found.
+    goto :exit
+)
+
+echo Using drive letter !mydriveletter!: for our tests
+echo.
+
+:: Define an array of hash algorithms and their corresponding container files
+set "algorithms[0]=sha512,test.sha512.hc"
+set "algorithms[1]=whirlpool,test.whirlpool.hc"
+set "algorithms[2]=sha256,test.sha256.hc"
+set "algorithms[3]=blake2s,test.blake2s.hc"
+set "algorithms[4]=streebog,test.streebog.hc"
+
+:: Loop through each algorithm
+for /L %%i in (0,1,4) do (
+    for /F "tokens=1,2 delims=," %%a in ("!algorithms[%%i]!") do (
+        set "hash=%%a"
+        set "container=%%b"
+        
+        if exist "!container!" (
+            call :mount_and_measure "!hash!" "!container!" "Normal" "!PASSWORD!"
+            call :mount_and_measure "!hash!" "!container!" "Hidden" "!HIDDEN_PASSWORD!"
+            echo.
+        )
+    )
+)
+
+:: Autodetect test
+call :availablevolume testvolume || goto :exit
+
+call :measure_time "Wrong Password (PRF Auto-detection)" ^
+    "/volume !testvolume! /l !mydriveletter! /password wrongpassword /q /silent /m ro"
+
+echo.
+goto :exit
+
+:: Subroutine to mount a volume and measure the time taken
+:mount_and_measure
+setlocal 
+set "hash=%~1"
+set "container=%~2"
+set "type=%~3"
+set "volumepassword=%~4"
+
+call :measure_time "%hash% (%type%)" ^
+    "/volume !container! /hash !hash! /l !mydriveletter! /password !volumepassword! /q /silent /m ro"
+
+if not exist !mydriveletter!:\ (
+    echo ERROR: Drive letter !mydriveletter!: does not exist after mount operation.
+    goto :exit
+)
+
+"!VERACRYPT_PATH!" /dismount !mydriveletter! /silent /q
+exit /b
+
+:: Subroutine to measure the time taken for a command to execute
+:measure_time
+setlocal 
+set "oper=%~1"
+set "command=%~2"
+
+for /F "tokens=1-4 delims=:.," %%a in ("!time!") do set /A "start=(((%%a*60)+1%%b %% 100)*60+1%%c %% 100)*100+1%%d %% 100"
+
+"!VERACRYPT_PATH!" %command%
+
+for /F "tokens=1-4 delims=:.," %%a in ("!time!") do set /A "end=(((%%a*60)+1%%b %% 100)*60+1%%c %% 100)*100+1%%d %% 100"
+
+set /A elapsed=end-start
+set /A hh=elapsed/(60*60*100), rest=elapsed%%(60*60*100), mm=rest/(60*100), rest%%=60*100, ss=rest/100, cc=rest%%100
+if %hh% lss 10 set hh=0%hh%
+if %mm% lss 10 set mm=0%mm%
+if %ss% lss 10 set ss=0%ss%
+if %cc% lss 10 set cc=0%cc%
+
+echo %oper% = %hh%:%mm%:%ss%,%cc%
+exit /b
+
+rem Finds a free drive letter.
+rem
+rem Parameters:
+rem     %1 = Output variable name.
+rem
+rem Example:
+rem     call :freedrive mydriveletter && goto :cont
+rem     echo ERROR: No free drive letter found.
+rem     goto :EOF
+rem     :cont
+rem     echo Found drive letter: %mydriveletter%
+:freedrive
+setlocal EnableDelayedExpansion
+set exitcode=0
+set "output_var=%~1"
+for %%i in (C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z) do (
+    set "drive=%%i:"
+    rem If 'subst' fails, the drive letter is already in use.
+    rem This way we can even detect optical drives that have a drive
+    rem letter but no media in them, a case that goes undetected when
+    rem using 'if exist'.
+    subst !drive! %SystemDrive%\ >nul
+    if !errorlevel! == 0 (
+        subst !drive! /d >nul
+		set "drive=%%i"
+        goto :freedrive0
+    )
+)
+set exitcode=1
+set drive=
+:freedrive0
+endlocal & set "%output_var%=%drive%" & exit /b %exitcode%
+
+:: Subroutine to find an available volume
+:availablevolume
+setlocal EnableDelayedExpansion
+set exitcode=0
+set "output_var=%~1"
+for %%i in (test.sha512.hc,test.sha256.hc,test.whirlpool.hc,test.blake2s.hc) do (
+    if exist %%i (
+        set "volume=%%i"
+        goto :availablevolume0
+    )
+)
+set exitcode=1
+set volume=
+:availablevolume0
+endlocal & set "%output_var%=%volume%" & exit /b %exitcode%
+
+:exit
+
+pause

contrib/EncryptData.ps1

@@ -0,0 +1,278 @@
+<#
+.SYNOPSIS
+This PowerShell script is used to create a VeraCrypt container with minimal size to hold a copy of the given input file or directory.
+
+.DESCRIPTION
+This script takes as input a file path or directory path and a container path.
+If the container path is not specified, it defaults to the same as the input path with a ".hc" extension.
+The script calculates the minimal size needed to hold the input file or directory in a VeraCrypt container.
+It then creates a VeraCrypt container with the specified path and the calculated size using exFAT filesystem.
+Finally, the container is mounted, the input file or directory is copied to the container and the container is dismounted.
+
+.PARAMETER inputPath
+The file path or directory path to be encrypted in the VeraCrypt container.
+
+.PARAMETER containerPath
+The desired path for the VeraCrypt container. If not specified, it defaults to the same as the input path with a ".hc" extension.
+
+.EXAMPLE
+.\EncryptData.ps1 -inputPath "C:\MyFolder" -containerPath "D:\MyContainer.hc"
+.\EncryptData.ps1 "C:\MyFolder" "D:\MyContainer.hc"
+.\EncryptData.ps1 "C:\MyFolder"
+
+.NOTES
+Author: Mounir IDRASSI
+Email: mounir.idrassi@idrix.fr
+Date: 26 July 2024
+License: This script is licensed under the Apache License 2.0
+#>
+
+# parameters
+param(
+    [Parameter(Mandatory=$true)]
+    [string]$inputPath,
+    [string]$containerPath
+)
+function ConvertTo-AbsolutePath {
+    param (
+        [Parameter(Mandatory=$true)]
+        [string]$Path
+    )
+
+    if ([System.IO.Path]::IsPathRooted($Path)) {
+        return $Path
+    }
+    
+    return Join-Path -Path (Get-Location) -ChildPath $Path
+}
+
+# Convert input path to fully qualified path
+$inputPath = ConvertTo-AbsolutePath -Path $inputPath
+
+# Check if input path exists
+if (-not (Test-Path $inputPath)) {
+    Write-Host "The specified input path does not exist. Please provide a valid input path."
+    exit 1
+}
+
+$inputPath = (Resolve-Path -Path $inputPath).Path
+
+# Set container path if not specified
+if ([string]::IsNullOrWhiteSpace($containerPath)) {
+    $containerPath = "${inputPath}.hc"
+} else {
+    $containerPath = ConvertTo-AbsolutePath -Path $containerPath
+}
+
+# Check if container path already exists
+if (Test-Path $containerPath) {
+    Write-Host "The specified container path already exists. Please provide a unique path for the new container."
+    exit 1
+}
+
+# Full path to VeraCrypt executables
+$veracryptPath = "C:\Program Files\VeraCrypt"  # replace with your actual path
+$veraCryptExe = Join-Path $veracryptPath "VeraCrypt.exe"
+$veraCryptFormatExe = Join-Path $veracryptPath "VeraCrypt Format.exe"
+
+# Constants used to calculate the size of the exFAT filesystem
+$InitialVBRSize = 32KB
+$BackupVBRSize = 32KB
+$InitialFATSize = 128KB
+$ClusterSize = 32KB # TODO : make this configurable
+$UpCaseTableSize = 128KB # Typical size
+
+function Get-ExFATSizeRec {
+    param(
+        [string]$Path,
+        [uint64] $TotalSize
+    )
+
+    # Constants
+    $BaseMetadataSize = 32
+    $DirectoryEntrySize = 32
+
+    try {
+        # Get the item (file or directory) at the provided path
+        $item = Get-Item -Path $Path -ErrorAction Stop
+
+        # Calculate metadata size
+        $fileNameLength = $item.Name.Length
+        $metadataSize = $BaseMetadataSize + ($fileNameLength * 2)
+
+        # Calculate directory entries
+        if ($fileNameLength -gt 15) {
+            $numDirEntries = [math]::Ceiling($fileNameLength / 15) + 1
+        } else {
+            $numDirEntries = 2
+        }
+        $dirEntriesSize = $numDirEntries * $DirectoryEntrySize
+
+        # Add metadata, file size, and directory entries size to $TotalSize
+        $TotalSize += $metadataSize + $dirEntriesSize
+
+
+        if ($item.PSIsContainer) {
+            # It's a directory
+            $childItems = Get-ChildItem -Path $Path -ErrorAction Stop
+
+            foreach ($childItem in $childItems) {
+                # Recursively call this function for each child item
+                $TotalSize = Get-ExFATSizeRec -Path $childItem.FullName -TotalSize $TotalSize
+            }
+        } else {
+            # It's a file
+
+            # Calculate actual file size and round it up to the nearest multiple of $ClusterSize
+            $fileSize = $item.Length
+            $totalFileSize = [math]::Ceiling($fileSize / $ClusterSize) * $ClusterSize
+
+            # Add metadata, file size, and directory entries size to $TotalSize
+            $TotalSize += $totalFileSize
+        }
+    } catch {
+        Write-Error "Error processing item at path ${Path}: $_"
+    }
+
+    return $TotalSize
+}
+
+function Get-ExFATSize {
+    param(
+        [string]$Path
+    )
+
+    try {
+        # Initialize total size
+        $totalSize = $InitialVBRSize + $BackupVBRSize + $InitialFATSize + $UpCaseTableSize
+
+        # Call the recursive function
+        $totalSize = Get-ExFATSizeRec -Path $Path -TotalSize $totalSize
+
+        # Add the root directory to $totalSize
+        $totalSize += $ClusterSize
+
+        # Calculate the size of the Bitmap Allocation Table
+        $numClusters = [math]::Ceiling($totalSize / $ClusterSize)
+        $bitmapSize = [math]::Ceiling($numClusters / 8)
+        $totalSize += $bitmapSize
+
+        # Adjust the size of the FAT
+        $fatSize = $numClusters * 4
+        $totalSize += $fatSize - $InitialFATSize
+		
+        # Add safety factor to account for potential filesystem overhead
+        # For smaller datasets (<100MB), we add 1% or 64KB (whichever is larger)
+        # For larger datasets (>=100MB), we add 0.1% or 1MB (whichever is larger)
+        # This scaled approach ensures adequate extra space without excessive overhead
+        $safetyFactor = if ($totalSize -lt 100MB) {
+            [math]::Max(64KB, $totalSize * 0.01)
+        } else {
+            [math]::Max(1MB, $totalSize * 0.001)
+        }
+        $totalSize += $safetyFactor
+
+        # Return the minimum disk size needed to store the exFAT filesystem
+        return $totalSize
+
+    } catch {
+        Write-Error "Error calculating exFAT size for path ${Path}: $_"
+        return 0
+    }
+}
+
+# Calculate size of the container
+$containerSize = Get-ExFATSize -Path $inputPath
+
+# Convert to MB and round up to the nearest MB
+$containerSize = [math]::Ceiling($containerSize / 1MB)
+
+# Add extra space for VeraCrypt headers, reserved areas, and potential alignment requirements
+# We use a sliding scale to balance efficiency for small datasets and adequacy for large ones:
+# - For very small datasets (<10MB), add 1MB
+# - For small to medium datasets (10-100MB), add 2MB
+# - For larger datasets (>100MB), add 1% of the total size
+# This approach ensures sufficient space across a wide range of dataset sizes
+if ($containerSize -lt 10) {
+    $containerSize += 1  # Add 1 MB for very small datasets
+} elseif ($containerSize -lt 100) {
+    $containerSize += 2  # Add 2 MB for small datasets
+} else {
+    $containerSize += [math]::Ceiling($containerSize * 0.01)  # Add 1% for larger datasets
+}
+
+# Ensure a minimum container size of 2 MB
+$containerSize = [math]::Max(2, $containerSize)
+
+# Specify encryption algorithm, and hash algorithm
+$encryption = "AES"
+$hash = "sha512"
+
+# Create a SecureString password
+$password = Read-Host -AsSecureString -Prompt "Enter your password"
+
+# Create a PSCredential object
+$cred = New-Object System.Management.Automation.PSCredential ("username", $password)
+
+Write-Host "Creating VeraCrypt container `"$containerPath`" ..."
+
+# Create file container using VeraCrypt Format
+# TODO: Add a switch to VeraCrypt Format to allow specifying the cluster size to use for the container
+$veraCryptFormatArgs = "/create `"$containerPath`" /size `"${containerSize}M`" /password $($cred.GetNetworkCredential().Password) /encryption $encryption /hash $hash /filesystem `"exFAT`" /quick /silent"
+Start-Process $veraCryptFormatExe -ArgumentList $veraCryptFormatArgs -NoNewWindow -Wait
+
+# Check that the container was successfully created
+if (-not (Test-Path $containerPath)) {
+    Write-Host "An error occurred while creating the VeraCrypt container."
+    exit 1
+}
+
+# Get a list of currently used drive letters
+$driveLetter = Get-Volume | Where-Object { $_.DriveLetter -ne $null } | Select-Object -ExpandProperty DriveLetter
+
+# Find the first available drive letter
+$unusedDriveLetter = (70..90 | ForEach-Object { [char]$_ } | Where-Object { $_ -notin $driveLetter })[0]
+
+# If no available drive letter was found, print an error message and exit the script
+if ($null -eq $unusedDriveLetter) {
+    # delete the file container that was created
+    Remove-Item -Path $containerPath -Force
+    Write-Error "No available drive letters found. Please free up a drive letter and try again."
+    exit 1
+}
+
+Write-Host "Mounting the newly created VeraCrypt container..."
+
+# Mount the container to the chosen drive letter as removable media
+Start-Process $veraCryptExe -ArgumentList "/volume `"$containerPath`" /letter $unusedDriveLetter /m rm /password $($cred.GetNetworkCredential().Password) /quit" -NoNewWindow -Wait
+
+# Check if the volume has been mounted successfully
+$mountedDriveRoot = "${unusedDriveLetter}:\"
+if (-not (Test-Path -Path $mountedDriveRoot)) {
+    # Volume mount failed
+    Write-Error "Failed to mount the volume. Please make sure VeraCrypt.exe is working correctly."
+    # delete the file container that was created
+    Remove-Item -Path $containerPath -Force
+    exit 1
+}
+
+Write-Host "Copying data to the mounted VeraCrypt container..."
+
+# Copy the file or directory to the mounted drive
+if (Test-Path -Path $inputPath -PathType Container) {
+    # For directories
+    Copy-Item -Path $inputPath -Destination "$($unusedDriveLetter):\" -Recurse
+} else {
+    # For files
+    Copy-Item -Path $inputPath -Destination "$($unusedDriveLetter):\"
+}
+
+Write-Host "Copying completed. Dismounting the VeraCrypt container..."
+
+# give some time for the file system to flush the data to the disk
+Start-Sleep -Seconds 5
+
+# Dismount the volume
+Start-Process $veraCryptExe -ArgumentList "/dismount $unusedDriveLetter /quit" -NoNewWindow -Wait
+
+Write-Host "VeraCrypt container created successfully."

doc/chm/VeraCrypt.hhc

@@ -0,0 +1,449 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Table Of Contents">
+		<param name="Local" value="Documentation.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Preface">
+		<param name="Local" value="Preface.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Introduction">
+		<param name="Local" value="Introduction.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Beginner's Tutorial ">
+		<param name="Local" value="Beginner's Tutorial.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="VeraCrypt Volume ">
+		<param name="Local" value="VeraCrypt Volume.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Creating a New VeraCrypt Volume">
+			<param name="Local" value="Creating New Volumes.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Favorite Volumes">
+			<param name="Local" value="Favorite Volumes.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="System Favorite Volumes">
+			<param name="Local" value="System Favorite Volumes.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="System Encryption">
+		<param name="Local" value="System Encryption.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Hidden Operating System">
+			<param name="Local" value="Hidden Operating System.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Operating Systems Supported for System Encryption">
+			<param name="Local" value="Supported Systems for System Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt Rescue Disk">
+			<param name="Local" value="VeraCrypt Rescue Disk.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Plausible Deniability">
+		<param name="Local" value="Plausible Deniability.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Hidden Volume">
+			<param name="Local" value="Hidden Volume.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Protection of Hidden Volumes Against Damage">
+				<param name="Local" value="Protection of Hidden Volumes.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Security Requirements and Precautions Pertaining to Hidden Volumes">
+				<param name="Local" value="Security Requirements for Hidden Volumes.html">
+				</OBJECT>
+		</UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Hidden Operating System">
+			<param name="Local" value="VeraCrypt Hidden Operating System.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Main Program Window">
+		<param name="Local" value="Main Program Window.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Program Menu">
+			<param name="Local" value="Program Menu.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Mounting Volumes">
+			<param name="Local" value="Mounting VeraCrypt Volumes.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Normal Dismount vs Force Dismount ">
+		<param name="Local" value="Normal Dismount vs Force Dismount.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Avoid Third-Party File Extensions">
+		<param name="Local" value="Avoid Third-Party File Extensions.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Parallelization">
+		<param name="Local" value="Parallelization.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Pipelining">
+		<param name="Local" value="Pipelining.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Hardware acceleration">
+		<param name="Local" value="Hardware Acceleration.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Hot keys">
+		<param name="Local" value="Hot Keys.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Keyfiles">
+		<param name="Local" value="Keyfiles in VeraCrypt.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Security Tokens &amp; Smart Cards">
+		<param name="Local" value="Security Tokens & Smart Cards.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Portable Mode">
+		<param name="Local" value="Portable Mode.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="TrueCrypt Support">
+		<param name="Local" value="TrueCrypt Support.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Converting TrueCrypt Volumes &amp; Partitions">
+		<param name="Local" value="Converting TrueCrypt volumes and partitions.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Conversion Guide for Versions 1.26 and Later">
+		<param name="Local" value="Conversion_Guide_VeraCrypt_1.26_and_Later.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Default Mount Parameters">
+		<param name="Local" value="Default Mount Parameters.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Language Packs">
+		<param name="Local" value="Language Packs.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Encryption Algorithms">
+		<param name="Local" value="Encryption Algorithms.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="AES">
+			<param name="Local" value="AES.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Camellia">
+			<param name="Local" value="Camellia.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Kuznyechik">
+			<param name="Local" value="Kuznyechik.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Serpent">
+			<param name="Local" value="Serpent.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Twofish">
+			<param name="Local" value="Twofish.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Cascades of ciphers">
+			<param name="Local" value="Cascades.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Hash Algorithms">
+		<param name="Local" value="Hash Algorithms.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="BLAKE2s-256">
+			<param name="Local" value="BLAKE2s-256.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="SHA-256">
+			<param name="Local" value="SHA-256.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="SHA-512">
+			<param name="Local" value="SHA-512.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Whirlpool">
+			<param name="Local" value="Whirlpool.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Streebog">
+			<param name="Local" value="Streebog.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Supported Operating Systems">
+		<param name="Local" value="Supported Operating Systems.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Command Line Usage">
+		<param name="Local" value="Command Line Usage.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Security Model">
+		<param name="Local" value="Security Model.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Security Requirements And Precautions">
+		<param name="Local" value="Security Requirements and Precautions.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Data Leaks">
+			<param name="Local" value="Data Leaks.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Paging File">
+				<param name="Local" value="Paging File.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Memory Dump Files">
+				<param name="Local" value="Memory Dump Files.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Hibernation File">
+				<param name="Local" value="Hibernation File.html">
+				</OBJECT>
+		</UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Unencrypted Data in RAM">
+			<param name="Local" value="Unencrypted Data in RAM.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt RAM Encryption">
+			<param name="Local" value="VeraCrypt RAM Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt Memory Protection">
+			<param name="Local" value="VeraCrypt Memory Protection.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Physical Security">
+			<param name="Local" value="Physical Security.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Malware">
+			<param name="Local" value="Malware.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Multi-User Environment">
+			<param name="Local" value="Multi-User Environment.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Authenticity and Integrity">
+			<param name="Local" value="Authenticity and Integrity.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Choosing Passwords and Keyfiles">
+			<param name="Local" value="Choosing Passwords and Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Changing Passwords and Keyfiles">
+			<param name="Local" value="Changing Passwords and Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Trim Operation">
+			<param name="Local" value="Trim Operation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Wear-Leveling">
+			<param name="Local" value="Wear-Leveling.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Reallocated Sectors">
+			<param name="Local" value="Reallocated Sectors.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Defragmenting">
+			<param name="Local" value="Defragmenting.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Journaling File Systems">
+			<param name="Local" value="Journaling File Systems.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Volume Clones">
+			<param name="Local" value="Volume Clones.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Additional Security Requirements and Precautions">
+			<param name="Local" value="Additional Security Requirements and Precautions.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="How To Back Up Securely">
+		<param name="Local" value="How to Back Up Securely.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Miscellaneous">
+		<param name="Local" value="Miscellaneous.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Using VeraCrypt Without Administrator Privileges">
+			<param name="Local" value="Using VeraCrypt Without Administrator Privileges.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Sharing Over Network">
+			<param name="Local" value="Sharing over Network.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt Background Task">
+			<param name="Local" value="VeraCrypt Background Task.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Volume Mounted as Removable Medium">
+			<param name="Local" value="Removable Medium Volume.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt System Files &amp; Application Data">
+			<param name="Local" value="VeraCrypt System Files.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="How To Remove Encryption">
+			<param name="Local" value="Removing Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Uninstalling VeraCrypt">
+			<param name="Local" value="Uninstalling VeraCrypt.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Digital Signatures">
+			<param name="Local" value="Digital Signatures.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Troubleshooting">
+		<param name="Local" value="Troubleshooting.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Incompatibilities">
+		<param name="Local" value="Incompatibilities.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Known Issues and Limitations">
+		<param name="Local" value="Issues and Limitations.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Frequently Asked Questions">
+		<param name="Local" value="FAQ.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Technical Details">
+		<param name="Local" value="Technical Details.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Notation">
+			<param name="Local" value="Notation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Encryption Scheme">
+			<param name="Local" value="Encryption Scheme.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Modes of Operation">
+			<param name="Local" value="Modes of Operation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Header Key Derivation, Salt, and Iteration Count">
+			<param name="Local" value="Header Key Derivation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Random Number Generator">
+			<param name="Local" value="Random Number Generator.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Keyfiles">
+			<param name="Local" value="Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="PIM">
+			<param name="Local" value="Personal Iterations Multiplier (PIM).html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt Volume Format Specification">
+			<param name="Local" value="VeraCrypt Volume Format Specification.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Compliance with Standards and Specifications">
+			<param name="Local" value="Standard Compliance.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Source Code">
+			<param name="Local" value="Source Code.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Building VeraCrypt From Source">
+			<param name="Local" value="CompilingGuidelines.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Windows Build Guide">
+				<param name="Local" value="CompilingGuidelineWin.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Linux Build Guide">
+				<param name="Local" value="CompilingGuidelineLinux.html">
+				</OBJECT>
+		</UL>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Contact">
+		<param name="Local" value="Contact.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Legal Information">
+		<param name="Local" value="Legal Information.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Version History">
+		<param name="Local" value="Release Notes.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Acknowledgements">
+		<param name="Local" value="Acknowledgements.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="References">
+		<param name="Local" value="References.html">
+		</OBJECT>
+</UL>
+</BODY></HTML>

doc/chm/VeraCrypt.hhk

@@ -0,0 +1,13 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+<LI> <OBJECT type="text/sitemap">
+     <param name="Name" value="Table Of Contents">
+     <param name="Local" value="Documentation.html">
+     </OBJECT>
+
+</UL>
+</BODY></HTML>

doc/chm/VeraCrypt.hhp

@@ -0,0 +1,191 @@
+[OPTIONS]
+Compatibility=1.1 or later
+Compiled file=VeraCrypt User Guide.chm
+Contents file=VeraCrypt.hhc
+Default topic=Documentation.html
+Display compile progress=No
+Full-text search=Yes
+Index file=VeraCrypt.hhk
+Language=0x409 English (United States)
+Title=VeraCrypt User Guide
+
+[FILES]
+Acknowledgements.html
+Additional Security Requirements and Precautions.html
+AES.html
+arrow_right.gif
+Authenticity and Integrity.html
+Authors.html
+Avoid Third-Party File Extensions.html
+bank_30x30.png
+BC_Logo_30x30.png
+BCH_Logo_30x30.png
+Beginner's Tutorial.html
+Beginner's Tutorial_Image_001.jpg
+Beginner's Tutorial_Image_002.jpg
+Beginner's Tutorial_Image_003.jpg
+Beginner's Tutorial_Image_004.jpg
+Beginner's Tutorial_Image_005.jpg
+Beginner's Tutorial_Image_007.jpg
+Beginner's Tutorial_Image_008.jpg
+Beginner's Tutorial_Image_009.jpg
+Beginner's Tutorial_Image_010.jpg
+Beginner's Tutorial_Image_011.jpg
+Beginner's Tutorial_Image_012.jpg
+Beginner's Tutorial_Image_013.jpg
+Beginner's Tutorial_Image_014.jpg
+Beginner's Tutorial_Image_015.jpg
+Beginner's Tutorial_Image_016.jpg
+Beginner's Tutorial_Image_017.jpg
+Beginner's Tutorial_Image_018.jpg
+Beginner's Tutorial_Image_019.jpg
+Beginner's Tutorial_Image_020.jpg
+Beginner's Tutorial_Image_021.jpg
+Beginner's Tutorial_Image_022.jpg
+Beginner's Tutorial_Image_023.gif
+Beginner's Tutorial_Image_024.gif
+Beginner's Tutorial_Image_034.png
+BLAKE2s-256.html
+Camellia.html
+Cascades.html
+Changing Passwords and Keyfiles.html
+Choosing Passwords and Keyfiles.html
+Command Line Usage.html
+CompilingGuidelineLinux.html
+CompilingGuidelines.html
+CompilingGuidelineWin.html
+Contact.html
+Contributed Resources.html
+Conversion_Guide_VeraCrypt_1.26_and_Later.html
+Converting TrueCrypt volumes and partitions.html
+Converting TrueCrypt volumes and partitions_truecrypt_convertion.jpg
+Creating New Volumes.html
+Data Leaks.html
+Default Mount Parameters.html
+Default Mount Parameters_VeraCrypt_password_using_default_parameters.png
+Defragmenting.html
+Digital Signatures.html
+Disclaimers.html
+Documentation.html
+Donation.html
+Donation_donate.gif
+Donation_donate_CHF.gif
+Donation_donate_Dollars.gif
+Donation_donate_Euros.gif
+Donation_donate_GBP.gif
+Donation_donate_PLN.gif
+Donation_donate_YEN.gif
+Donation_VeraCrypt_Bitcoin_small.png
+Donation_VeraCrypt_BitcoinCash.png
+Donation_VeraCrypt_Litecoin.png
+Donation_VeraCrypt_Monero.png
+Encryption Algorithms.html
+Encryption Scheme.html
+FAQ.html
+Favorite Volumes.html
+flattr-badge-large.png
+gf2_mul.gif
+Hardware Acceleration.html
+Hash Algorithms.html
+Header Key Derivation.html
+Hibernation File.html
+Hidden Operating System.html
+Hidden Volume.html
+Home_facebook_veracrypt.png
+Home_reddit.png
+Home_utilities-file-archiver-3.png
+Home_VeraCrypt_Default_Mount_Parameters.png
+Home_VeraCrypt_menu_Default_Mount_Parameters.png
+Hot Keys.html
+How to Back Up Securely.html
+Incompatibilities.html
+Introduction.html
+Issues and Limitations.html
+Journaling File Systems.html
+Keyfiles in VeraCrypt.html
+Keyfiles in VeraCrypt_Image_040.gif
+Keyfiles.html
+Kuznyechik.html
+Language Packs.html
+Legal Information.html
+liberapay_donate.svg
+LTC_Logo_30x30.png
+Main Program Window.html
+Malware.html
+Memory Dump Files.html
+Miscellaneous.html
+Modes of Operation.html
+Monero_Logo_30x30.png
+Mounting VeraCrypt Volumes.html
+Multi-User Environment.html
+Notation.html
+Paging File.html
+Parallelization.html
+paypal_30x30.png
+Personal Iterations Multiplier (PIM).html
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step2.png
+Physical Security.html
+Pipelining.html
+Plausible Deniability.html
+Portable Mode.html
+Preface.html
+Program Menu.html
+Protection of Hidden Volumes.html
+Protection of Hidden Volumes_Image_027.jpg
+Protection of Hidden Volumes_Image_028.jpg
+Protection of Hidden Volumes_Image_029.jpg
+Protection of Hidden Volumes_Image_030.jpg
+Protection of Hidden Volumes_Image_031.jpg
+Random Number Generator.html
+Reallocated Sectors.html
+References.html
+Release Notes.html
+Removable Medium Volume.html
+Removing Encryption.html
+Security Model.html
+Security Requirements and Precautions.html
+Security Requirements for Hidden Volumes.html
+Security Tokens & Smart Cards.html
+Serpent.html
+SHA-256.html
+SHA-512.html
+Sharing over Network.html
+Source Code.html
+Standard Compliance.html
+Streebog.html
+styles.css
+Supported Operating Systems.html
+Supported Systems for System Encryption.html
+System Encryption.html
+System Favorite Volumes.html
+Technical Details.html
+Trim Operation.html
+Troubleshooting.html
+TrueCrypt Support.html
+TrueCrypt Support_truecrypt_mode_gui.jpg
+twitter_veracrypt.PNG
+Twofish.html
+Unencrypted Data in RAM.html
+Uninstalling VeraCrypt.html
+Using VeraCrypt Without Administrator Privileges.html
+VeraCrypt Background Task.html
+VeraCrypt Hidden Operating System.html
+VeraCrypt License.html
+VeraCrypt Memory Protection.html
+VeraCrypt RAM Encryption.html
+VeraCrypt Rescue Disk.html
+VeraCrypt System Files.html
+VeraCrypt Volume Format Specification.html
+VeraCrypt Volume.html
+VeraCrypt128x128.png
+Volume Clones.html
+Wear-Leveling.html
+Whirlpool.html
+
+[INFOTYPES]
+

doc/chm/create_chm.bat

@@ -0,0 +1,11 @@
+PATH=%PATH%;C:\Program Files (x86)\HTML Help Workshop
+
+set CHMBUILDPATH=%~dp0
+cd %CHMBUILDPATH%
+
+xcopy /E ..\html\* .
+
+hhc VeraCrypt.hhp
+
+del /F /Q *.html *.css *.jpg *.gif *.png *.svg
+rmdir /s /Q CompilingGuidelineWin ru

doc/html/AES.html

@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Encryption%20Algorithms.html">Encryption Algorithms</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="AES.html">AES</a>
+</p></div>
+
+<div class="wikidoc">
+<h1>AES</h1>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+The Advanced Encryption Standard (AES) specifies a FIPS-approved cryptographic algorithm (Rijndael, designed by Joan Daemen and Vincent Rijmen, published in 1998) that may be used by US federal departments and agencies to cryptographically protect sensitive
+ information [3]. VeraCrypt uses AES with 14 rounds and a 256-bit key (i.e., AES-256, published in 2001) operating in
+<a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+XTS mode</a> (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Modes of Operation</a>).</div>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+In June 2003, after the NSA (US National Security Agency) conducted a review and analysis of AES, the U.S. CNSS (Committee on National Security Systems) announced in [1] that the design and strength of AES-256 (and AES-192) are sufficient to protect classified
+ information up to the Top Secret level. This is applicable to all U.S. Government Departments or Agencies that are considering the acquisition or use of products incorporating the Advanced Encryption Standard (AES) to satisfy Information Assurance requirements
+ associated with the protection of national security systems and/or national security information [1].</div>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<a href="Camellia.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Acknowledgements.html

@@ -0,0 +1,58 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Acknowledgements.html">Acknowledgements</a>
+</p></div>
+<div class="wikidoc">
+<div>
+<h1>Acknowledgements</h1>
+<p>We would like to thank the following people:</p>
+<p>The TrueCrypt Developers team who have done an amazing job over the course of 10 years. Without their hard work, VeraCrypt would not exist today.</p>
+<p>Paul Le Roux for making his E4M source code available. TrueCrypt 1.0 was derived from E4M and some parts of the E4M source code are still incorporated in the latest version of the TrueCrypt source code.</p>
+<p>Brian Gladman, who wrote the excellent AES, Twofish, and SHA-512 routines.</p>
+<p>Peter Gutmann for his paper on random numbers, and for creating his cryptlib, which was the source of parts of the random number generator source code.</p>
+<p>Wei Dai, who wrote the Serpent and RIPEMD-160 and Whirlpool routines.</p>
+<p>Tom St Denis, the author of LibTomCrypt which includes compact SHA-256 routines.</p>
+<p>Mark Adler and Jean-loup Gailly, who wrote the zlib library.</p>
+<p>The designers of the encryption algorithms, hash algorithms, and the mode of operation:</p>
+<p>Horst Feistel, Don Coppersmith, Walt Tuchmann, Lars Knudsen, Ross Anderson, Eli Biham, Bruce Schneier, David Wagner, John Kelsey, Niels Ferguson, Doug Whiting, Chris Hall, Joan Daemen, Vincent Rijmen, Carlisle Adams, Stafford Tavares, Phillip Rogaway, Hans
+ Dobbertin, Antoon Bosselaers, Bart Preneel, Paulo S. L. M. Barreto.</p>
+<p>Andreas Becker for designing VeraCrypt logo and icons.</p>
+<p>Xavier de Carn&eacute; de Carnavalet who proposed a speed optimization for PBKDF2 that reduced mount/boot time by half.</p>
+<p>kerukuro for cppcrypto library (http://cppcrypto.sourceforge.net/) from which Kuznyechik cipher implementation was taken.</p>
+<p><br>
+Dieter Baron and Thomas Klausner who wrote the libzip library.</p>
+<p><br>
+Jack Lloyd who wrote the SIMD optimized Serpent implementation.</p>
+<p>All the others who have made this project possible, all who have morally supported us, and all who sent us bug reports or suggestions for improvements.</p>
+<p>Thank you very much.</p>
+</div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Additional Security Requirements and Precautions.html

@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Security%20Requirements%20and%20Precautions.html">Security Requirements and Precautions</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Additional%20Security%20Requirements%20and%20Precautions.html">Additional Security Requirements and Precautions</a>
+</p></div>
+
+<div class="wikidoc">
+<div>
+<h1>Additional Security Requirements and Precautions</h1>
+<p>In addition to the requirements and precautions described in this chapter (<a href="Security%20Requirements%20and%20Precautions.html"><em>Security Requirements and Precautions</em></a>), you must follow and keep in
+ mind the security requirements, precautions, and limitations listed in the following chapters and sections:</p>
+<ul>
+<li><a href="How%20to%20Back%20Up%20Securely.html"><em><strong>How to Back Up Securely</strong></em></a>
+</li><li><a href="Issues%20and%20Limitations.html"><em><strong>Limitations</strong></em></a>
+</li><li><a href="Security%20Model.html"><em><strong>Security Model</strong></em></a>
+</li><li><a href="Security%20Requirements%20for%20Hidden%20Volumes.html"><em><strong>Security Requirements and Precautions Pertaining to Hidden Volumes</strong></em></a>
+</li><li><a href="Plausible%20Deniability.html"><em><strong>Plausible Deniability</strong></em></a>
+</li></ul>
+<p>See also: <a href="Digital%20Signatures.html">
+<em>Digital Signatures</em></a></p>
+</div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Authenticity and Integrity.html

@@ -0,0 +1,49 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Security%20Requirements%20and%20Precautions.html">Security Requirements and Precautions</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Authenticity%20and%20Integrity.html">Authenticity and Integrity</a>
+</p></div>
+
+<div class="wikidoc">
+<div>
+<h1>Authenticity and Integrity</h1>
+<p>VeraCrypt uses encryption to preserve the <em>confidentiality</em> of data it encrypts. VeraCrypt neither preserves nor verifies the integrity or authenticity of data it encrypts or decrypts. Hence, if you allow an adversary to modify data encrypted by VeraCrypt,
+ he can set the value of any 16-byte block of the data to a random value or to a previous value, which he was able to obtain in the past. Note that the adversary cannot choose the value that you will obtain when VeraCrypt decrypts the modified block &mdash;
+ the value will be random &mdash; unless the attacker restores an older version of the encrypted block, which he was able to obtain in the past. It is your responsibility to verify the integrity and authenticity of data encrypted or decrypted by VeraCrypt (for
+ example, by using appropriate third-party software).<br>
+<br>
+See also: <a href="Physical%20Security.html">
+<em>Physical Security</em></a>, <a href="Security%20Model.html">
+<em>Security Model</em></a></p>
+</div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Authors.html

@@ -0,0 +1,42 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="VeraCrypt%20Volume.html">VeraCrypt Volume</a>
+</p></div>
+
+<div class="wikidoc">
+<h2>Authors</h2>
+<p>Mounir IDRASSI (<a href="https://www.idrix.fr" target="_blank">IDRIX</a>, <a href="https://fr.linkedin.com/in/idrassi" target="_blank">
+https://fr.linkedin.com/in/idrassi</a>) is the creator and main developer of VeraCrypt. He managed all development and deployment aspects on all supported platforms (Windows,Linux and OSX).</p>
+<p>Alex Kolotnikov (<a href="https://ru.linkedin.com/in/alex-kolotnikov-6625568b" target="_blank">https://ru.linkedin.com/in/alex-kolotnikov-6625568b</a>) is the author of VeraCrypt EFI bootloader. He manages all aspects of EFI support and his strong expertise
+ helps bring new exciting features to VeraCrypt Windows system encryption.</p>
+<p>&nbsp;</p>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Avoid Third-Party File Extensions.html

@@ -0,0 +1,85 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Avoid%20Third-Party%20File%20Extensions.html">Avoid Third-Party File Extensions</a>
+</p></div>
+
+<div class="wikidoc">
+	<h1>Understanding the Risks of Using Third-Party File Extensions with VeraCrypt</h1>
+	<div>
+	  <p>While VeraCrypt provides robust encryption capabilities to secure your data, using third-party file extensions for File Containers or Keyfiles could risk making the encrypted data inaccessible.<br />
+	  This guide provides an in-depth explanation of the associated risks, and it outlines recommendations for best practices to mitigate these risks.</p>
+	</div>
+	
+	<h2>Risks Associated with File Containers</h2>
+	<div>
+	  <p>Using a third-party file extension for File Containers exposes you to several risks:</p>
+	  <ul>
+		<li>Overwritten Metadata: Third-party applications may update their metadata, which could overwrite crucial parts of the File Container.</li>
+		<li>Unintentional Changes: Accidentally launching a File Container with a third-party application could modify its metadata without your consent.</li>
+		<li>Container Corruption: These actions could render the container unreadable or unusable.</li>
+		<li>Data Loss: The data within the container might be permanently lost if the container becomes corrupted.</li>
+	  </ul>
+	</div>
+	
+	<h2>Risks Associated with Keyfiles</h2>
+	<div>
+	  <p>Similar risks are associated with Keyfiles:</p>
+	  <ul>
+		<li>Keyfile Corruption: Inadvertently modifying a Keyfile with a third-party application can make it unusable for decryption.</li>
+		<li>Overwritten Data: Third-party applications may overwrite the portion of the Keyfile that VeraCrypt uses for decryption.</li>
+		<li>Unintentional Changes: Accidental changes can make it impossible to mount the volume unless you have an unaltered backup of the Keyfile.</li>
+	  </ul>
+	</div>
+	
+	<h2>Examples of Extensions to Avoid</h2>
+	<div>
+	  <p>Avoid using the following types of third-party file extensions:</p>
+	  <ul>
+		<li>Media Files: Picture, audio, and video files are subject to metadata changes by their respective software.</li>
+		<li>Archive Files: Zip files can be easily modified, which could disrupt the encrypted volume.</li>
+		<li>Executable Files: Software updates can modify these files, making them unreliable as File Containers or Keyfiles.</li>
+		<li>Document Files: Office and PDF files can be automatically updated by productivity software, making them risky to use.</li>
+	  </ul>
+	</div>
+	
+	<h2>Recommendations</h2>
+	<div>
+	  <p>For secure usage, consider the following best practices:</p>
+	  <ul>
+		<li>Use neutral file extensions for File Containers and Keyfiles to minimize the risk of automatic file association.</li>
+		<li>Keep secure backups of your File Containers and Keyfiles in locations isolated from network access.</li>
+		<li>Disable auto-open settings for the specific file extensions you use for VeraCrypt File Containers and Keyfiles.</li>
+		<li>Always double-check file associations and be cautious when using a new device or third-party application.</li>
+	  </ul>
+	</div>
+	
+<div class="ClearBoth"></div></body></html>

doc/html/BLAKE2s-256.html

@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Hash%20Algorithms.html">Hash Algorithms</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="BLAKE2s-256.html">BLAKE2s-256</a>
+</p></div>
+
+<div class="wikidoc">
+<h1>BLAKE2s-256</h1>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<p>
+BLAKE2 is a cryptographic hash function based on BLAKE, created by Jean-Philippe Aumasson, Samuel Neves, Zooko Wilcox-O'Hearn, and Christian Winnerlein. It was announced on December 21, 2012. The design goal was to replace the widely used, but broken, MD5 and SHA-1 algorithms in applications requiring high performance in software. BLAKE2 provides better security than SHA-2 and similar to that of SHA-3 (e.g. immunity to length extension, indifferentiability from a random oracle, etc...).<br/>
+BLAKE2 removes addition of constants to message words from BLAKE round function, changes two rotation constants, simplifies padding, adds parameter block that is XOR'ed with initialization vectors, and reduces the number of rounds from 16 to 12 for BLAKE2b (successor of BLAKE-512), and from 14 to 10 for BLAKE2s (successor of BLAKE-256).<br/>
+BLAKE2b and BLAKE2s are specified in RFC 7693.
+</p>
+<p>
+VeraCrypt uses only BLAKE2s with its maximum output size of 32-bytes (256 bits).
+</p>
+</div>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<a href="SHA-256.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/Beginner's Tutorial.html

@@ -0,0 +1,207 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="/code/">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Beginner's%20Tutorial.html">Beginner's Tutorial</a>
+</p></div>
+
+<div class="wikidoc">
+<h1>Beginner's Tutorial</h1>
+<h2>How to Create and Use a VeraCrypt Container</h2>
+<p>This chapter contains step-by-step instructions on how to create, mount, and use a VeraCrypt volume. We strongly recommend that you also read the other sections of this manual, as they contain important information.</p>
+<h4>STEP 1:</h4>
+<p>If you have not done so, download and install VeraCrypt. Then launch VeraCrypt by double-clicking the file VeraCrypt.exe or by clicking the VeraCrypt shortcut in your Windows Start menu.</p>
+<h4>STEP 2:</h4>
+<p><img src="Beginner's Tutorial_Image_001.jpg" alt=""><br>
+<br>
+The main VeraCrypt window should appear. Click <strong>Create Volume </strong>(marked with a red rectangle for clarity).</p>
+<h4>STEP 3:</h4>
+<p><img src="Beginner's Tutorial_Image_002.jpg" alt=""><br>
+<br>
+The VeraCrypt Volume Creation Wizard window should appear.<br>
+<br>
+In this step you need to choose where you wish the VeraCrypt volume to be created. A VeraCrypt volume can reside in a file, which is also called container, in a partition or drive. In this tutorial, we will choose the first option and create a VeraCrypt volume
+ within a file.<br>
+<br>
+As the option is selected by default, you can just click <strong>Next</strong>.</p>
+<p>Note: In the following steps, the screenshots will show only the right-hand part of the Wizard window.</p>
+<h4>STEP 4:</h4>
+<p><img src="Beginner's Tutorial_Image_003.jpg" alt=""><br>
+<br>
+In this step you need to choose whether to create a standard or hidden VeraCrypt volume. In this tutorial, we will choose the former option and create a standard VeraCrypt volume.<br>
+<br>
+As the option is selected by default, you can just click <strong>Next</strong>.</p>
+<h4>STEP 5:</h4>
+<p><img src="Beginner's Tutorial_Image_004.jpg" alt=""><br>
+<br>
+In this step you have to specify where you wish the VeraCrypt volume (file container) to be created. Note that a VeraCrypt container is just like any normal file. It can be, for example, moved or deleted as any normal file. It also needs a filename, which you
+ will choose in the next step.<br>
+<br>
+Click <strong>Select File</strong>.<br>
+<br>
+The standard Windows file selector should appear (while the window of the VeraCrypt Volume Creation Wizard remains open in the background).</p>
+<h4>STEP 6:</h4>
+<p><img src="Beginner's Tutorial_Image_005.jpg" alt=""><br>
+<br>
+In this tutorial, we will create our VeraCrypt volume in the folder F<em>:\Data\ </em>
+and the filename of the volume (container) will be <em>MyVolume.hc </em>(as can be seen in the screenshot above). You may, of course, choose any other filename and location you like (for example, on a USB memory stick). Note that the file
+<em>MyVolume.hc </em>does not exist yet &ndash; VeraCrypt will create it.</p>
+<p>IMPORTANT: Note that VeraCrypt will <em>not </em>encrypt any existing files (when creating a VeraCrypt file container). If you select an existing file in this step, it will be overwritten and replaced by the newly created volume (so the overwritten file
+ will be <em>lost</em>, <em>not </em>encrypted). You will be able to encrypt existing files (later on) by moving them to the VeraCrypt volume that we are creating now.*</p>
+<p>Select the desired path (where you wish the container to be created) in the file selector. Type the desired container file name in the
+<strong>Filename </strong>box.<br>
+<br>
+Click <strong>Save</strong>.<br>
+<br>
+The file selector window should disappear.<br>
+<br>
+In the following steps, we will return to the VeraCrypt Volume Creation Wizard.</p>
+<p>* Note that after you copy existing unencrypted files to a VeraCrypt volume, you should securely erase (wipe) the original unencrypted files. There are software tools that can be used for the purpose of secure erasure (many of them are free).</p>
+<h4>STEP 7:</h4>
+<p><img src="Beginner's Tutorial_Image_007.jpg" alt=""><br>
+<br>
+In the Volume Creation Wizard window, click <strong>Next</strong>.</p>
+<h4>STEP 8:</h4>
+<p><img src="Beginner's Tutorial_Image_008.jpg" alt=""><br>
+<br>
+Here you can choose an encryption algorithm and a hash algorithm for the volume. If you are not sure what to select here, you can use the default settings and click
+<strong>Next </strong>(for more information, see chapters <a href="Encryption Algorithms.html">
+<em>Encryption Algorithms</em></a> and <a href="Hash%20Algorithms.html">
+<em>Hash Algorithms</em></a>).</p>
+<h4>STEP 9:</h4>
+<p><img src="Beginner's Tutorial_Image_009.jpg" alt=""><br>
+<br>
+Here we specify that we wish the size of our VeraCrypt container to be 250 megabyte. You may, of course, specify a different size. After you type the desired size in the input field (marked with a red rectangle), click
+<strong>Next</strong>.</p>
+<h4>STEP 10:</h4>
+<p><img src="Beginner's Tutorial_Image_010.jpg" alt=""><br>
+<br>
+This is one of the most important steps. Here you have to choose a good volume password. Read carefully the information displayed in the Wizard window about what is considered a good password.<br>
+<br>
+After you choose a good password, type it in the first input field. Then re-type it in the input field below the first one and click
+<strong>Next</strong>.</p>
+<p>Note: The button <strong>Next </strong>will be disabled until passwords in both input fields are the same.</p>
+<h4>STEP 11:</h4>
+<p><img src="Beginner's Tutorial_Image_011.jpg" alt=""><br>
+<br>
+Move your mouse as randomly as possible within the Volume Creation Wizard window at least until the randomness indicator becomes green. The longer you move the mouse, the better (moving the mouse for at least 30 seconds is recommended). This significantly increases
+ the cryptographic strength of the encryption keys (which increases security).<br>
+<br>
+Click <strong>Format</strong>.<br>
+<br>
+Volume creation should begin. VeraCrypt will now create a file called <em>MyVolume.hc
+</em>in the folder F<em>:\Data\ </em>(as we specified in Step 6). This file will be a VeraCrypt container (it will contain the encrypted VeraCrypt volume). Depending on the size of the volume, the volume creation may take a long time. After it finishes, the
+ following dialog box will appear:<br>
+<br>
+<img src="Beginner's Tutorial_Image_012.jpg" alt=""><br>
+<br>
+Click <strong>OK </strong>to close the dialog box.</p>
+<h4>STEP 12:</h4>
+<p><img src="Beginner's Tutorial_Image_013.jpg" alt=""><br>
+<br>
+We have just successfully created a VeraCrypt volume (file container). In the VeraCrypt Volume Creation Wizard window, click
+<strong>Exit</strong>.<br>
+<br>
+The Wizard window should disappear.<br>
+<br>
+In the remaining steps, we will mount the volume we just created. We will return to the main VeraCrypt window (which should still be open, but if it is not, repeat Step 1 to launch VeraCrypt and then continue from Step 13.)</p>
+<h4>STEP 13:</h4>
+<p><img src="Beginner's Tutorial_Image_014.jpg" alt=""><br>
+<br>
+Select a drive letter from the list (marked with a red rectangle). This will be the drive letter to which the VeraCrypt container will be mounted.<br>
+<br>
+Note: In this tutorial, we chose the drive letter M, but you may of course choose any other available drive letter.</p>
+<h4>STEP 14:</h4>
+<p><img src="Beginner's Tutorial_Image_015.jpg" alt=""><br>
+<br>
+Click <strong>Select File</strong>.<br>
+<br>
+The standard file selector window should appear.</p>
+<h4>STEP 15:</h4>
+<p><img src="Beginner's Tutorial_Image_016.jpg" alt=""><br>
+<br>
+In the file selector, browse to the container file (which we created in Steps 6-12) and select it. Click
+<strong>Open </strong>(in the file selector window).<br>
+<br>
+The file selector window should disappear.<br>
+<br>
+In the following steps, we will return to the main VeraCrypt window.</p>
+<h4>STEP 16:</h4>
+<p><img src="Beginner's Tutorial_Image_017.jpg" alt=""><br>
+<br>
+In the main VeraCrypt window, click <strong>Mount</strong>. Password prompt dialog window should appear.</p>
+<h4>STEP 17:</h4>
+<p><img src="Beginner's Tutorial_Image_018.jpg" alt=""><br>
+<br>
+Type the password (which you specified in Step 10) in the password input field (marked with a red rectangle).</p>
+<h4>STEP 18:</h4>
+<p><img src="Beginner's Tutorial_Image_019.jpg" alt=""><br>
+<br>
+Select the PRF algorithm that was used during the creation of the volume (SHA-512 is the default PRF used by VeraCrypt). If you don&rsquo;t remember which PRF was used, just leave it set to &ldquo;autodetection&rdquo; but the mounting process will take more
+ time. Click <strong>OK</strong> after entering the password.<br>
+<br>
+VeraCrypt will now attempt to mount the volume. If the password is incorrect (for example, if you typed it incorrectly), VeraCrypt will notify you and you will need to repeat the previous step (type the password again and click
+<strong>OK</strong>). If the password is correct, the volume will be mounted.</p>
+<h4>FINAL STEP:</h4>
+<p><img src="Beginner's Tutorial_Image_020.jpg" alt=""><br>
+<br>
+We have just successfully mounted the container as a virtual disk M:<br>
+<br>
+The virtual disk is entirely encrypted (including file names, allocation tables, free space, etc.) and behaves like a real disk. You can save (or copy, move, etc.) files to this virtual disk and they will be encrypted on the fly as they are being written.<br>
+<br>
+If you open a file stored on a VeraCrypt volume, for example, in media player, the file will be automatically decrypted to RAM (memory) on the fly while it is being read.</p>
+<p>Important: Note that when you open a file stored on a VeraCrypt volume (or when you write/copy a file to/from the VeraCrypt volume) you will not be asked to enter the password again. You need to enter the correct password only when mounting the volume.</p>
+<p>You can open the mounted volume, for example, by selecting it on the list as shown in the screenshot above (blue selection) and then double-clicking on the selected item.</p>
+<p>You can also browse to the mounted volume the way you normally browse to any other types of volumes. For example, by opening the &lsquo;<em>Computer</em>&rsquo; (or &lsquo;<em>My Computer</em>&rsquo;) list and double clicking the corresponding drive letter
+ (in this case, it is the letter M).<br>
+<br>
+<img src="Beginner's Tutorial_Image_021.jpg" alt=""><br>
+<br>
+You can copy files (or folders) to and from the VeraCrypt volume just as you would copy them to any normal disk (for example, by simple drag-and-drop operations). Files that are being read or copied from the encrypted VeraCrypt volume are automatically decrypted
+ on the fly in RAM (memory). Similarly, files that are being written or copied to the VeraCrypt volume are automatically encrypted on the fly in RAM (right before they are written to the disk).<br>
+<br>
+Note that VeraCrypt never saves any decrypted data to a disk &ndash; it only stores them temporarily in RAM (memory). Even when the volume is mounted, data stored in the volume is still encrypted. When you restart Windows or turn off your computer, the volume
+ will be dismounted and all files stored on it will be inaccessible (and encrypted). Even when power supply is suddenly interrupted (without proper system shut down), all files stored on the volume will be inaccessible (and encrypted). To make them accessible
+ again, you have to mount the volume. To do so, repeat Steps 13-18.</p>
+<p>If you want to close the volume and make files stored on it inaccessible, either restart your operating system or dismount the volume. To do so, follow these steps:<br>
+<br>
+<img src="Beginner's Tutorial_Image_022.jpg" alt=""><br>
+<br>
+Select the volume from the list of mounted volumes in the main VeraCrypt window (marked with a red rectangle in the screenshot above) and then click
+<strong>Dismount </strong>(also marked with a red rectangle in the screenshot above). To make files stored on the volume accessible again, you will have to mount the volume. To do so, repeat Steps 13-18.</p>
+<h2>How to Create and Use a VeraCrypt-Encrypted Partition/Device</h2>
+<p>Instead of creating file containers, you can also encrypt physical partitions or drives (i.e., create VeraCrypt device-hosted volumes). To do so, repeat the steps 1-3 but in the step 3 select the second or third option. Then follow the remaining instructions
+ in the wizard. When you create a device-hosted VeraCrypt volume within a <em>non-system
+</em>partition/drive, you can mount it by clicking <em>Auto-Mount Devices </em>in the main VeraCrypt window. For information pertaining to encrypted
+<em>system </em>partition/drives, see the chapter <a href="System%20Encryption.html">
+<em>System Encryption</em></a>.</p>
+<p>Important: <em>We strongly recommend that you also read the other chapters of this manual, as they contain important information that has been omitted in this tutorial for simplicity.</em></p>
+</div>
+</body></html>