Description
Description
Latest builds showing earlier merged signed commits as No known key found for this signature in database.
New merged commits are unsigned.
New initialized repositories are created unsigned with SIGNING_KEY = default and not created at all with error 500 when specifying KEYID instead of default and adding SIGNING_NAME, SIGNING_EMAIL as per docs.
2022/06/13 20:54:23 ...s/repository/init.go:349:initRepoCommit() [E] Failed to commit: [commit --author='Ilya Pavlov [email protected]' -m Initial commit -SB0292765]: Stdout:
Error: exit status 128 - error: gpg failed to sign the data
fatal: failed to write commit object
- error: gpg failed to sign the data
fatal: failed to write commit object
2022/06/13 20:54:23 ...ers/web/repo/repo.go:195:handleCreateError() [E] CreatePost: initRepository: initRepoCommit: git commit: exit status 128 - error: gpg failed to sign the data
fatal: failed to write commit object
- error: gpg failed to sign the data
fatal: failed to write commit object
Server GPG key without expiry date not changed in last two years, git or gitea relevant config parameters either.
git config --global user.signingkey B0292765
git config --global commit.gpgsign true[repository.signing]
SIGNING_KEY = default
INITIAL_COMMIT = always
CRUD_ACTIONS = pubkey, twofa, parentsigned
WIKI = never
MERGES = pubkey, twofa, basesigned, commitssignedWhen i create manual test commits inside container they are signed.
Gitea Version
1.17.0+dev-709-gff82a1831
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker image gitea/gitea:dev
Database
PostgreSQL