Maybe it's too hot today and my brain isn't working. Can anyone with experience/insight into Forgejo and Gitea explain to me what the point is of the server signing commits (e.g. merge, initial commit, wiki etc.)? Maybe I'm missing something obvious, but the whole point of signing commits is as an authenticity check. If an attacker would gain access to a user's account that has the permission to trigger any of these actions, the signature mechanism does not allow differentiating between a legitimate and compromised commit. The only case I can think of where this might be useful is if someone would try to pass off an unsigned commit to look like it has been done by the server, whereas legitimate commits by the server have been signed. Without an option to block unsigned commits entirely this seems a bit like security theater though, if my threat model isn't entirely wrong. Thoughts?


