HCVault.Native
1.6.0
See the version list below for details.
dotnet add package HCVault.Native --version 1.6.0
NuGet\Install-Package HCVault.Native -Version 1.6.0
<PackageReference Include="HCVault.Native" Version="1.6.0" />
<PackageVersion Include="HCVault.Native" Version="1.6.0" />
<PackageReference Include="HCVault.Native" />
paket add HCVault.Native --version 1.6.0
#r "nuget: HCVault.Native, 1.6.0"
#:package HCVault.Native@1.6.0
#addin nuget:?package=HCVault.Native&version=1.6.0
#tool nuget:?package=HCVault.Native&version=1.6.0
HCVault.Native
NuGet package with the prebuilt native libraries of hcvault-core — a
portable build of the VeraCrypt volume core behind a small C API (vcapi.h):
create, open and modify VeraCrypt containers, normal and hidden volumes, all
cipher/KDF combinations, keyfiles, PIM, header re-encryption, exFAT via the
bundled FatFs (ChaN R0.15).
The package follows the standard NuGet runtimes/ layout:
| Runtime | Library |
|---|---|
win-x64, win-x86, win-arm64 |
hcvault-core.dll |
linux-x64 |
libhcvault-core.so |
android-arm64, android-arm, android-x86, android-x64 |
libhcvault-core.so (API 21+, 16 KB-page aligned) |
Usage
Reference HCVault.Core (the managed wrapper) and build your application
with a RuntimeIdentifier — HCVault.Core depends on this package, so the
matching library is pulled in automatically, copied to your output (or
packaged into the APK lib/<abi>/ on Android) and found by the wrapper's
loader. Reference this package explicitly only to force a different version.
Building without a RuntimeIdentifier copies no native library; either set
one (-r linux-x64 …), place the library next to the application manually,
or point the VCNATIVE_HOME environment variable at it.
Need a platform not listed above (macOS, other architectures)? Build the core
from the repository sources instead: it is a plain CMake project
(cmake -S native -B build && cmake --build build), and HCVault.Core
picks up manually placed libraries through the same probing rules.
License and provenance
Packaging and port layer: Apache-2.0. The vendored VeraCrypt sources are
under the VeraCrypt license (LICENSE-VeraCrypt.txt in this package),
dual-licensed Apache-2.0 / TrueCrypt 3.0. FatFs is BSD-style.
This project is independent and not affiliated with IDRIX or the VeraCrypt project. The code was written with AI assistance and has not been security-audited.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on HCVault.Native:
| Package | Downloads |
|---|---|
|
HCVault.Core
Managed wrapper around the VeraCrypt volume core: create, open, read and write VeraCrypt encrypted containers (normal and hidden volumes, all cipher/KDF combinations, keyfiles, PIM) without mounting them. Pulls in the matching HCVault.Native package (prebuilt native libraries for Windows, Linux and Android) automatically; build your own from the repository sources with CMake if you need another platform. |
GitHub repositories
This package is not used by any popular GitHub repositories.
1.6.0: the exFAT bridge accepts an empty path as the volume root; otherwise no native changes - version-aligned with HCVault.Core 1.6.0 (keyfile streams, folder import/export, automatic HCVault.Native dependency). Volumes are compatible with 1.4.x/1.5.x (same vcapi v4).