Release asset verification

Use this page before installing or redistributing a VaultPilot release asset. Verify the official release, the Ed25519-signed update manifest and the exact file hashes as one trust decision.

Release state

The current release is VaultPilot 3.0.3, published on July 29, 2026 as a stable release.

Trust model for this release

VaultPilot-3.0.3-x64.msi is not Authenticode-signed. For updates that VaultPilot manages, the trust gate is the Ed25519 signature on vaultpilot-update.json plus the manifest’s exact MSI SHA-256, file size and allowed release address. The downloaded MSI must match that hash before Windows Installer starts.

This exception does not apply to other downloads or MSI files placed on the server by hand; those still need a valid Authenticode signature or a configured signer. A future manifest that names a signer also requires that signer.

VaultPilot 3.0.3 components

ComponentVersionDelivery
VaultPilot Enterprise Vault Console3.0.3VaultPilot-3.0.3-x64.msi and vaultpilot-update.json
Chromium Browser Extension1.3.3Chrome Web Store is primary; the release ZIP is an archive/emergency fallback
Offline Share Decrypter1.2.1Versioned ZIP and JSON metadata
VaultPilot DC Agent Service1.2.27Versioned PowerShell asset and JSON metadata
VaultPilot Backup Tool3.0.0Bundled support component
VaultPilot Log Collector3.0.2Bundled support component

Public asset set

AssetSizeSHA-256
VaultPilot-3.0.3-x64.msi65,463,39623e42e7a2b46e0b02337054cd975afc8a0c475d52cf6ef090a0567ae5d08a218
vaultpilot-update.json1,124a51ff079b5f9908ea48dee738ec9a550ccda51cfa5e974b2429bf35881ffc2f0
vaultpilot-update-public.pub113f2dba0438e5f9fad87d34413b690ca9db0cd9181deb19caaed19f0c730c06139
vaultpilot-browser-vault-extension.zip209,2332682932082b9d141d36e6546b449a1168b50ac4c473e1c20cf65090f738c2e4c
vaultpilot-extension-update.json2577ba50fa6188f6ce42db555154a140e65d50787dd8ff422528ea0ff1b897aafdc
vaultpilot-share-decrypter.zip51,566e72cef76a1a8389339ea75469e6467b908cd51cd7e8f6381fcb61910eb9af756
vaultpilot-share-decrypter.json2185d4af2cd0be93f7d553a37def1446d71962c9d0f5a8403038455197659ba7da8
vaultpilot-dc-agent.ps1241,65858ef4b043068b36a8dce29d3159a41b047e32720329987941e9d245e7d4a8b98
vaultpilot-dc-agent.json21344b0ee50d300a1b5e4368b91e68ce45057330bb75591e6d2ead4b17e1f65999b

Verification steps

  1. Download vaultpilot-update.json, vaultpilot-update-public.pub and VaultPilot-3.0.3-x64.msi from the official v3.0.3 release only.
  2. Verify the manifest signature with the public key, then confirm its server version, URL, file name, file size and SHA-256 match the release asset.
  3. Verify all downloaded asset hashes against this table before internal redistribution.
  4. Expect Get-AuthenticodeSignature to report NotSigned for this MSI. Do not substitute an unrelated certificate or bypass the manifest/hash checks.
  5. Install and update the browser extension through Chrome Web Store; use the ZIP only for documented fallback cases.

Windows verification commands

Get-ChildItem -File |
  Where-Object { $_.Name -eq 'VaultPilot-3.0.3-x64.msi' -or $_.Name -like 'vaultpilot-*' } |
  Select-Object Name,Length

Get-FileHash .\VaultPilot-3.0.3-x64.msi -Algorithm SHA256
Get-FileHash .\vaultpilot-* -Algorithm SHA256

Get-AuthenticodeSignature .\VaultPilot-3.0.3-x64.msi |
  Format-List Status,StatusMessage,SignerCertificate

If the asset name, file size, SHA-256, manifest signature or manifest URL differs from the published values, do not install or redistribute the package.

Back to Documentation