Code signing is the process of applying a digital signature to a piece of code so that it can be later verified to ensure
that it has not been modified after it was signed. This can help establish that the code came from a trusted source and reduce
the risk of installing malicious code. In
Niagara, all stock modules are signed and verified at runtime.
In
Niagara 4.8 and later, there is added support for the signing and verification of third party modules. Third party module signing is
still optional in most cases, but this will gradually shift to a requirement over the course of the next three releases.
CAUTION: A security best practice is to encourage the original authors of a module to sign their own code. Signing a module on behalf
of a 3rd party should be done only as a last option, and only if you trust the authors.
For more details on code signing, see “Code Signing” in the Niagara Developer Guide (
Niagara 4.6 and later).