aiforge

346 MB

Tree: ba5ba4e8af

Author	SHA1	Message	Date
zeripath	620ff39c58	Fix the intermittent TestGPGGit failures (#9360 ) * Fix the intermittent TestGPGGit failures Reattempt to open the listener if the port is busy with a delay up to a second Switch from generating a private key each time, just use a known good key	6 years ago
zeripath	51da2413b5	Missed defer prepareTestEnv (#9285 ) * onGiteaRun should defer the cleanup from prepareTestEnv * Some more missed defers	6 years ago
zeripath	92f4c6463e	Yet another attempt to fix the intermittent failure of gpg git test (#9146 ) * Yet another attempt to fix the race in gpg_git_test * add some fail nows * Need to set preparetestenv * Ensure that http messages go to the correct server	6 years ago
zeripath	38dea67a7e	Fix "data race" in testlogger (#9159 ) * Fix data race in testlogger * Update git_helper_for_declarative_test.go	6 years ago
zeripath	c70802a9f3	Fix intermittent GPG Git test failure (#8968 )	6 years ago
zeripath	76b8e9500e	Sign merges, CRUD, Wiki and Repository initialisation with gpg key (#7631 ) This PR fixes #7598 by providing a configurable way of signing commits across the Gitea instance. Per repository configurability and import/generation of trusted secure keys is not provided by this PR - from a security PoV that's probably impossible to do properly. Similarly web-signing, that is asking the user to sign something, is not implemented - this could be done at a later stage however. ## Features - [x] If commit.gpgsign is set in .gitconfig sign commits and files created through repofiles. (merges should already have been signed.) - [x] Verify commits signed with the default gpg as valid - [x] Signer, Committer and Author can all be different - [x] Allow signer to be arbitrarily different - We still require the key to have an activated email on Gitea. A more complete implementation would be to use a keyserver and mark external-or-unactivated with an "unknown" trust level icon. - [x] Add a signing-key.gpg endpoint to get the default gpg pub key if available - Rather than add a fake web-flow user I've added this as an endpoint on /api/v1/signing-key.gpg - [x] Try to match the default key with a user on gitea - this is done at verification time - [x] Make things configurable? - app.ini configuration done - [x] when checking commits are signed need to check if they're actually verifiable too - [x] Add documentation I have decided that adjusting the docker to create a default gpg key is not the correct thing to do and therefore have not implemented this.	6 years ago

6 Commits (ba5ba4e8af4026b8a2feeba767a8430bcc9dfa20)