Since the enablement of signature verification in swupd-client, the
signature creation step has been decoupled from swupd-server, and is
instead performed as a separate step in a DevOps flow. As a result of
this decoupling, the signature code in swupd-server has remained unused.
This commit removes all the signature creation code with the assumption
that the separate DevOps step is going to work better long-term. Also,
the existing signature creation support does not accord with
swupd-client's verification support.
Since the enablement of signature verification in swupd-client, the signature creation step has been decoupled from swupd-server, and is instead performed as a separate step in a DevOps flow. As a result of this decoupling, the signature code in swupd-server has remained unused.
This commit removes all the signature creation code with the assumption that the separate DevOps step is going to work better long-term. Also, the existing signature creation support does not accord with swupd-client's verification support.
An example of how Manifest.MoM files can be signed is found in the https://github.com/clearlinux/mixer-tools repo.