Skip to content
LogosPilot
Request private preview

Why verification matters

How release verification will work

Nothing on this page is downloadable yet, so there is nothing here to verify today. A church in the private preview receives a code-signed installer and can run both checks below on it. This page sets them out so that you know what you are checking and why.

There is nothing to verify yet

Availability
No signed release has been published

LogosPilot is in private preview. No installer has been published, so there is no file to check and no checksum to check it against.

The verification values appear together with the first signed release — the file name, the SHA-256 checksum and the signature status, published at the same moment as the file itself. We do not publish an installer and its checksum separately, because a checksum that arrives later verifies nothing about what you already downloaded.

Why verification matters

Software you download can be altered between our build and your machine — by an interrupted transfer, a proxy that rewrites files, or, rarely, by someone who intended to.

Verification is how you find out. It does not require trusting us: it compares what you have against a value we published in advance, and either it matches or it does not.

That is why the standard is published now, before there is anything to check. A verification procedure written on release day is a procedure nobody has had a chance to read.

Check the digital signature

The signature confirms that the installer was published by us and has not been altered since it was signed. Windows checks this for you, and you can inspect it yourself.

  1. Right-click the installer file and choose Properties.

  2. Open the Digital Signatures tab.

  3. Select the signature in the list and choose Details.

    The signer name shown must match LogosPilot LLC.

  4. Confirm that Windows reports the signature as valid.

What you should see

A valid signature, signed by LogosPilot LLC, with no warning that the certificate is untrusted or expired.

Check the checksum

The checksum is a fingerprint of the file's contents. If a single byte differs, the checksum differs. You will calculate it yourself in PowerShell, in the folder where you saved the installer, and compare it with the value LogosPilot publishes.

  1. Download the published installer.

  2. Confirm its digital signature, as described above.

  3. Calculate its SHA-256 checksum with Get-FileHash, naming the installer file and specifying the SHA256 algorithm.

    The exact command, with the real file name in it, is published alongside the release rather than guessed at here.

  4. Compare what PowerShell prints against the value published by LogosPilot. They must match exactly, character for character. Capitalisation does not matter.

  5. If they differ, stop. Do not install the file, and tell us.

    security@logospilot.com

No checksum is shown on this page

There is no release, so there is no value to display and nothing to copy. Publishing a specimen checksum, even an obviously fake one, would train the habit of comparing against whatever this page happens to show.

If a check does not match

Do not install the file. A mismatch has two possible causes, and they need different responses.

Most likely: an incomplete download

Delete the file, download it again, and check once more. An interrupted or resumed transfer is the common cause.

If it fails again, contact support@logospilot.com.

If it fails a second time, tell us

A repeated mismatch, or a signature that reports as invalid or untrusted, may mean the file was altered. That is a security matter and we want to hear about it directly.

security@logospilot.com

You do not need an account, and there is nothing to sign. Tell us what you saw and we will look at it.

Reporting something that turns out to be a bad download costs you a short email and costs us nothing. We would rather hear it.

Where to go next

Next steps

When the first release is published

The installer, its signature and its checksum are published together, and these checks become something you can actually run. Until then LogosPilot is in private preview.

Request private preview Contact security