Skip to content

fix(commit): reject SHA-256 signatures and non-UTF-8 messages - #36

Merged
wsehl merged 1 commit into
bstack/wsehl/28ffa5a0cccc4bd994b49d5e1e8186affrom
bstack/wsehl/feee043856314f52a15d170ea27e9381
Sep 29, 2026
Merged

wsehl merged 1 commit into
bstack/wsehl/28ffa5a0cccc4bd994b49d5e1e8186affrom
bstack/wsehl/feee043856314f52a15d170ea27e9381

Conversation

@wsehl

@wsehl wsehl commented Sep 29, 2026

Copy link
Copy Markdown
Owner

The signed-commit check only matched the gpgsig header, so commits
signed in SHA-256 repositories (gpgsig-sha256) were rewritten with a
signature that no longer verifies.

Commit objects are read as UTF-8, so a message stored in another
encoding would be corrupted on rewrite and in the PR text. Such
commits are now rejected with a clear error instead.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) noreply@anthropic.com

The signed-commit check only matched the `gpgsig` header, so commits
signed in SHA-256 repositories (`gpgsig-sha256`) were rewritten with a
signature that no longer verifies.

Commit objects are read as UTF-8, so a message stored in another
`encoding` would be corrupted on rewrite and in the PR text. Such
commits are now rejected with a clear error instead.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
bstack-id: feee043856314f52a15d170ea27e9381
@wsehl
wsehl added this pull request to stack #43 September 29, 2026 10:33
@wsehl
wsehl merged commit e2994e0 into main Sep 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant