Verifying a BAVIS download: a minute well spent
Before you install BAVIS, you can check that the file really comes from Benešl Automation and has not changed on the way. It takes a minute and it is a good habit for any software that controls a plant.
What protects what
| What you download | How it is protected | Who verifies |
|---|---|---|
Windows installerBAVIS_Setup_*.exe | SHA-256 hash on this page and in SHA256SUMS.txt; no Authenticode signature yet | you, before running it |
Linux package.tar.gz, .deb | SHA-256 hash | you, before installing |
Project or communication module package.bavispkg | Benešl Automation Ed25519 signature and a hash of every file | BAVIS itself during installation |
Update.whu | Ed25519 signature | BAVIS itself, it rejects an unsigned one |
1. SHA-256 hash
With every release we publish SHA-256 hashes, here on the website and in the SHA256SUMS.txt file next to the installer. The hash of the downloaded file must match the one on the website. If it does not, do not run the file and let us know.
- Windows (PowerShell):
Get-FileHash .\BAVIS_Setup_4.0.0.exe -Algorithm SHA256 - Without PowerShell (command prompt):
certutil -hashfile BAVIS_Setup_4.0.0.exe SHA256 - Linux and macOS:
sha256sum -c SHA256SUMS.txt --ignore-missing(macOS:shasum -a 256 -c SHA256SUMS.txt)
Checking all files against SHA256SUMS.txt in PowerShell
Run it in the folder with the downloaded files. It prints True for every file whose hash matches.
Get-Content .\SHA256SUMS.txt | ForEach-Object {
$o, $s = $_ -split '\s+', 2
if (Test-Path $s) { '{0} {1}' -f ((Get-FileHash $s -Algorithm SHA256).Hash.ToLower() -eq $o), $s }
}A hash only protects you if you compare it with a source other than the one the file came from. That is why the hashes are also here on benesl-automation.cz.
Release hashes
We will add the hashes with the release of BAVIS 4.0.
2. Windows SmartScreen warning
The BAVIS 4.0 installer does not have a code signature yet; we will add the signing certificate in a later version. Windows may therefore show a blue “Windows protected your PC” window when you run it.
What to do: first check the SHA-256 hash. If it matches, click More info and then Run anyway. User Account Control then shows “Unknown publisher”, which is expected for an unsigned installer.
- Company computer (AppLocker, WDAC, group policy): the administrator may block an unsigned installer. Allowing it by its SHA-256 hash is safer than an exception for a folder.
- Windows 11 with Smart App Control may block the installer without a “Run anyway” option. Do not switch the protection off for the installation: install BAVIS on another computer, use Linux or wait for the signed installer.
- Antivirus sometimes holds a new unsigned file for checking. In case of a false positive, send us the detection name and the file hash.
Once the installer is signed, you will see the publisher “Benešl Automation” in Properties → Digital Signatures.
3. Signed packages and updates
We sign project packages, communication module packages and updates with an Ed25519 key. The public keys are built into BAVIS and BAVIS checks the signature itself: when you upload a package in the interface, when installing from the installer and when updating. The interface shows “✓ verified – signed by Benešl Automation” or “community, unsigned”.
A project package without a valid signature is not installed. A community communication module only with an explicit “I install at my own risk” confirmation and an entry in the audit log. BAVIS rejects an unsigned or modified update.
Public keys
| Key (kid) | Ed25519 public key (base64) | Validity |
|---|---|---|
6a25b0a13c71ab4e2026 update key | 7Dq+p8ycE1kY/tUmpWfXgIwA2k2x4MmIARG/8F7tNRE= | until 31 Dec 2028 |
e511c2b850f9f714original shared key | EJZ8I72RTgDcsrSk7+lPmW3PX0Y5uONk84jI+LjRbyo= | older releases |
If something does not match
Do not run the file, delete it and download it again directly from benesl-automation.cz. If the hash still does not match, send us the file name, where you downloaded it from and the hash you got. Report a security issue according to our vulnerability reporting policy.