Skip to content

Conversation

@dscho
Copy link
Contributor

@dscho dscho commented Nov 11, 2025

It has been reported in #2028 that Git Credential Manager's .deb files cannot be validated with debsig-verify. A deeper investigation brought to light that the reason is a weak digest algorithm: debsigs calls gpg --opengpg which uses SHA-1, but debsig-verify rejects such weak signatures.

This was actually already fixed in debsigs, but current Ubuntu versions will not get those fixes, being stuck with older debsigs versions.

It's easy enough to work around, though, so just like microsoft/git#815, let's let Git Credential Manager's release workflow work around that.

This closes #2028

It has been reported in
#2028 that
Git Credential Manager's `.deb` files cannot be validated with
`debsig-verify`. A deeper investigation brought to light that the reason
is a weak digest algorithm: `debsigs` calls `gpg --opengpg` which uses
SHA-1, but `debsig-verify` rejects such weak signatures.

This was actually already fixed in `debsigs`, but current Ubuntu
versions will not get those fixes, being stuck with older `debsigs`
versions.

It's easy enough to work around, though, so let's do that.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho self-assigned this Nov 11, 2025
@dscho dscho requested a review from a team as a code owner November 11, 2025 09:10
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.

.deb package signed with a deprecated SHA1 algorithm

2 participants