DebOps Code Signing Policy¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119].
The configuration management code and other source code used by the DebOps Project and committed to its repositories  MUST be signed by a valid OpenPGP key of a DebOps Developer. For contributors it is RECOMMENDED to do the same.
Patches from DebOps Contributors MUST be reviewed by one of the DebOps Developers and the merge commit MUST by signed by the DebOps Developer for this patch to enter the DebOps Project. This should ensure that the last commit of every repository of the DebOps Project has a valid signature by a DebOps Developer.
This should allow for secure code authentication. That means that tampering with the code on the source code management platform can be reliable detected by DebOps Tools, DebOps Developers and all of the users of the Project and thus the integrity of the Project does not rely on centralized parties anymore (not yet implemented). Additionally, this ensures a trusted audit trail.
Refer to the debops-keyring where a copies of the OpenPGP keys are present which can be used to verify the signatures.
|||All repositories in the DebOps core project currently hosted at: https://github.com/debops/. This does not apply for DebOps Contrib.|
- Git Tools - Signing Your Work
- A Git Horror Story: Repository Integrity With Signed Commits
- What are the advantages and disadvantages of cryptographically signing commits and tags in Git?
- Discussion between drybjed and ypid
- PR of the initial code signing policy
- Issue "sign all git commits" started by @adrelanos (which also includes various pointers)