new Snapwatcher version using new CodeNotary integrity — Opvizor

We recently received a message from a certificate authority to renew our code signing digital certificate for roughly $500 a year. When we don’t renew, the certificate will expire and all of our customers might receive a Microsoft Windows warning.

Given the fact that Snapwatcher is a lightweight tool in a low price range, that’s quite a number. Especially, when you think of the benefits of that certificate. Our customer can see that this software has been signed with our digital certificate and that your downloaded file on your disk is the same file we provide on our Google storage share.

In the meantime there are more modern ways to proof the identity of the file author and the guarantee integrity, we deliver the new Snapwatcher version without a digital certificate based signature, but allow the verification by CodeNotary.

We are in good company with out decision and more will follow:

As our blog reader know, we always describe more than the marketing part — we explain the procedure step by step, from code to build, signature, upload and verification.

Nothing really changed for building your software, except that you don’t need to point to any certificate to be used.

We use Visual Studio to build our .net Application Snapwatcher.

This application is an online Windows App by default without a setup that requires an internet connection. As we have customers that have isolated environments we also build it locally and create a installer using Inno Setup.

The result is a setup file that installs the application on isolated systems (no internet access) or terminal services.

When the installer build completed successfully, the setup is automatically started for testing purposes.

We deliver Snapwatcher compressed as a zip file. The compression is not great, but at least customers can download the file without a dozen warning messages.

Therefore, we need to sign both files using CodeNotary. As CodeNotary integrates nicely into the Windows explorer, we can just right-click and sign the file. You can find the installer on the CodeNotary Github page: vchain-us/vcn

And the complete online help: CodeNotary help

Now both files are signed and can be verified by anyone using vcn or the Google Chrome browser extension.

What means Sign

Sign means that the vcn command calculates a unique, military-grade hash of the selected file. Afterwards that file is directly written to a distributed ledger (Ethereum-based blockchain) using the private key of the CodeNotary user ( in this case). There is no service in between that interferes.

By default files or code is signed private, not disclosing much information. If you want to sign public, you need to run the vcn command with the -public flag:

You will directly notice the different output, when verifying the file.

Is the file changed when signing?

Using the CodeNotary approach the file and the integrity and identity proof are not stored together. The file doesn’t get changed at all (in case of a certificate, the signature and the hash need to be added to the file) and the hash and signature are stored using the vChain CodeNotary distributed ledger technology (publicly accessible and verifiable).

Verify the file

Now that the files have been signed, everyone can verify them using vcn. Here you can also see the difference between private

and public signing, as more information are disclosed, like Filename or Signer.

Of course you can also verify the file immediately using the Browser extension.

or if you allow the system to check every download automatically:

As you can see, its extremely easy to check the integrity of the file. Using the vcn command you can also see the signer including email and filename. Many more attributes are currently in the making, so there will be a origin download url and many more features, that make downloads trustworthy.

Originally published at

Fullstack Monitoring, Analytics, Security: VMware, Docker, Kubernetes, Applications