While working on authentication and key management #49, I kept bumping into a nasty issue: Signing both requests and commits is not always possible. I need to have a fallback that has a lesser audit trail. I think adding an optional author field in Commits is a decent compromise. The commit will still be signed, but this time by the Server's default agent.
This is very similar to how git functions. If you edit a file on github.com, it will be signed by github, but authored by you. This means that we have to put away our cryptographic proof for authorship, but that's of course the entire point.
What this would allow me to do, is to introduce an /unsignedCommit endpoint that allows for some other authentication mechanism, such as OAuth or WebAuthn.
While working on authentication and key management #49, I kept bumping into a nasty issue: Signing both requests and commits is not always possible. I need to have a fallback that has a lesser audit trail. I think adding an optional
authorfield in Commits is a decent compromise. The commit will still be signed, but this time by the Server's default agent.This is very similar to how git functions. If you edit a file on github.com, it will be signed by github, but authored by you. This means that we have to put away our cryptographic proof for authorship, but that's of course the entire point.
What this would allow me to do, is to introduce an
/unsignedCommitendpoint that allows for some other authentication mechanism, such as OAuth or WebAuthn.