OBA

Security and antivirus results

OBA's Windows files are not code-signed. As proof of trust, every release is scanned on VirusTotal and the results are public on this page, next to the SHA-256 of each file.

Why the files are unsigned

Korvenium is a small, independent developer. A code-signing certificate is a yearly cost and is easiest to get as a company; we will get one once Korvenium is incorporated. Until then, Windows treats every new, rarely downloaded program as unknown and shows a SmartScreen warning (see below).

In place of a signature we publish two things for every release: the SHA-256 of each file, so you can check that your download is the file we built, and a public VirusTotal scan of it.

Scan results by release

Clean is the number of engines that found nothing (or called the file harmless) out of the engines that gave a verdict; engines that do not support the file type or timed out are not counted. If an engine flags a file, we show its name and the name it gave, and report it to the vendor as a false positive. Newest release first.

Loading scan results…

Check your download

Compute the SHA-256 of the file you downloaded and compare it with the table above. In Command Prompt:

certutil -hashfile OBA-Setup-1.5.0.exe SHA256

Or in PowerShell:

Get-FileHash .\OBA-Setup-1.5.0.exe

Use your file's name and version. If the value is different, do not open the file; write to [email protected].

"Windows protected your PC"

When you open the setup file you downloaded, Windows may show a blue window: "Windows protected your PC". This is not a virus warning; Windows shows it for any program that is not yet widely downloaded and has no digital signature.

OBA is made by a small independent team and does not have a code-signing certificate yet. Instead:

  • every release is scanned on VirusTotal by dozens of antivirus engines, and the results are public on our Security page;
  • the SHA-256 of the file you downloaded should match the one on that page.

To start the installer

  1. Click More info in the warning.
  2. The publisher shows as "Unknown publisher"; click the Run anyway button that appears.

You will only see this the first time.

To check the file yourself: in PowerShell, run Get-FileHash .\OBA-Setup-<version>.exe; the value must match the SHA-256 on the Security page. If it does not, do not open the file — contact us.

Contact

Found something suspicious or have a question? [email protected]. Back to the download page.