Connections sign commits with an SSH key and carry a commit identity #1816

Closed
opened 2026-11-08 13:04:14 +00:00 by sam · 2 comments
Owner

An operator sets, per forge connection, the commit author name and email and an SSH signing key (secret reference) in the dashboard. Commits the daemon makes through that connection carry that identity and an SSH signature that git verify-commit and the forge accept. The key never enters a task container.

Done when a configured connection produces signed, attributed commits.

An operator sets, per forge connection, the commit author name and email and an SSH signing key (secret reference) in the dashboard. Commits the daemon makes through that connection carry that identity and an SSH signature that git verify-commit and the forge accept. The key never enters a task container. Done when a configured connection produces signed, attributed commits.
sam closed this issue 2026-11-08 13:05:33 +00:00
Author
Owner

Done in ac98b68bd. Verified a signed commit with git verify-commit against an allowed-signers file.

Done in ac98b68bd. Verified a signed commit with git verify-commit against an allowed-signers file.
Author
Owner

Follow-up fa76f4c99: agent commits are made inside the container, so the identity and signature never applied. The daemon now re-authors and SSH-signs the unpublished commits at push time.

Follow-up fa76f4c99: agent commits are made inside the container, so the identity and signature never applied. The daemon now re-authors and SSH-signs the unpublished commits at push time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1816