-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Sign merges, CRUD, Wiki and Repository initialisation with gpg key #7631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
b205fdf
Enable use of default gpg key for signing commits
zeripath 9f8cdb5
fix more unix date uses
zeripath 35b68ce
Merge branch 'master' into web-sign
zeripath e5f8508
Merge branch 'master' into web-sign
zeripath 5e5d201
fix verification for provided key id and file response
zeripath c4fda14
Add some integration test for gpg signing
zeripath 483ac21
fix issue with default reason
zeripath 7d0ffa9
Merge branch 'master' into web-sign
zeripath 4c8487f
update vendor
zeripath dae22e7
Use gpg.error.not_signed_commit instead of unsigned for unsigned commits
zeripath f4a07a5
Restore old signing key, name, and email at end of gpg_git_test
zeripath b674f17
fix repofiles_delete_test
zeripath 52740e6
Make it possible to get per repository signing-keys
zeripath 09d771a
Update documentation
zeripath cf35ac6
Merge branch 'master' into web-sign
zeripath a7dca0b
Merge branch 'master' into web-sign
zeripath 5d827d5
Adjust the app.ini.sample to make SIGNING_* clearer
zeripath 83fc620
Fix duplicate declaration of modules/settings in file_test
zeripath 61bb5c2
Merge branch 'master' into web-sign
zeripath 942ccbe
Ensure early git functionality
zeripath d245253
Add functionality note
zeripath a1f4a0d
Oops -m is present since 1.7.2 on commit
zeripath e1979a7
Merge branch 'master' into web-sign
zeripath b03ca96
Update docs/content/doc/advanced/signing.en-us.md
zeripath 070a5c2
Merge branch 'master' into web-sign
zeripath 7a01822
Add swagger definitions
zeripath f9f14c0
Merge branch 'master' into web-sign
lafriks File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,162 @@ | ||
--- | ||
date: "2019-08-17T10:20:00+01:00" | ||
title: "GPG Commit Signatures" | ||
slug: "signing" | ||
weight: 20 | ||
toc: false | ||
draft: false | ||
menu: | ||
sidebar: | ||
parent: "advanced" | ||
name: "GPG Commit Signatures" | ||
weight: 20 | ||
identifier: "signing" | ||
--- | ||
|
||
# GPG Commit Signatures | ||
|
||
Gitea will verify GPG commit signatures in the provided tree by | ||
checking if the commits are signed by a key within the gitea database, | ||
or if the commit matches the default key for git. | ||
|
||
Keys are not checked to determine if they have expired or revoked. | ||
Keys are also not checked with keyservers. | ||
|
||
A commit will be marked with a grey unlocked icon if no key can be | ||
found to verify it. If a commit is marked with a red unlocked icon, | ||
it is reported to be signed with a key with an id. | ||
|
||
Please note: The signer of a commit does not have to be an author or | ||
committer of a commit. | ||
|
||
This functionality requires git >= 1.7.9 but for full functionality | ||
this requires git >= 2.0.0. | ||
|
||
## Automatic Signing | ||
|
||
There are a number of places where Gitea will generate commits itself: | ||
|
||
* Repository Initialisation | ||
* Wiki Changes | ||
* CRUD actions using the editor or the API | ||
* Merges from Pull Requests | ||
|
||
Depending on configuration and server trust you may want Gitea to | ||
sign these commits. | ||
|
||
## General Configuration | ||
|
||
Gitea's configuration for signing can be found with the | ||
`[repository.signing]` section of `app.ini`: | ||
|
||
```ini | ||
... | ||
[repository.signing] | ||
SIGNING_KEY = default | ||
SIGNING_NAME = | ||
SIGNING_EMAIL = | ||
INITIAL_COMMIT = always | ||
CRUD_ACTIONS = pubkey, twofa, parentsigned | ||
WIKI = never | ||
MERGES = pubkey, twofa, basesigned, commitssigned | ||
|
||
... | ||
``` | ||
|
||
### `SIGNING_KEY` | ||
|
||
The first option to discuss is the `SIGNING_KEY`. There are three main | ||
options: | ||
|
||
* `none` - this prevents Gitea from signing any commits | ||
* `default` - Gitea will default to the key configured within | ||
`git config` | ||
* `KEYID` - Gitea will sign commits with the gpg key with the ID | ||
`KEYID`. In this case you should provide a `SIGNING_NAME` and | ||
`SIGNING_EMAIL` to be displayed for this key. | ||
|
||
The `default` option will interrogate `git config` for | ||
`commit.gpgsign` option - if this is set, then it will use the results | ||
of the `user.signingkey`, `user.name` and `user.email` as appropriate. | ||
|
||
Please note: by adjusting git's `config` file within Gitea's | ||
repositories, `SIGNING_KEY=default` could be used to provide different | ||
signing keys on a per-repository basis. However, this is cleary not an | ||
ideal UI and therefore subject to change. | ||
|
||
### `INITIAL_COMMIT` | ||
|
||
This option determines whether Gitea should sign the initial commit | ||
when creating a repository. The possible values are: | ||
|
||
* `never`: Never sign | ||
* `pubkey`: Only sign if the user has a public key | ||
* `twofa`: Only sign if the user logs in with two factor authentication | ||
* `always`: Always sign | ||
|
||
Options other than `never` and `always` can be combined as a comma | ||
separated list. | ||
|
||
### `WIKI` | ||
|
||
This options determines if Gitea should sign commits to the Wiki. | ||
The possible values are: | ||
|
||
* `never`: Never sign | ||
* `pubkey`: Only sign if the user has a public key | ||
* `twofa`: Only sign if the user logs in with two factor authentication | ||
* `parentsigned`: Only sign if the parent commit is signed. | ||
* `always`: Always sign | ||
|
||
Options other than `never` and `always` can be combined as a comma | ||
separated list. | ||
|
||
### `CRUD_ACTIONS` | ||
|
||
This option determines if Gitea should sign commits from the web | ||
editor or API CRUD actions. The possible values are: | ||
|
||
* `never`: Never sign | ||
* `pubkey`: Only sign if the user has a public key | ||
* `twofa`: Only sign if the user logs in with two factor authentication | ||
* `parentsigned`: Only sign if the parent commit is signed. | ||
* `always`: Always sign | ||
|
||
Options other than `never` and `always` can be combined as a comma | ||
separated list. | ||
|
||
### `MERGES` | ||
|
||
This option determines if Gitea should sign merge commits from PRs. | ||
The possible options are: | ||
|
||
* `never`: Never sign | ||
* `pubkey`: Only sign if the user has a public key | ||
* `twofa`: Only sign if the user logs in with two factor authentication | ||
* `basesigned`: Only sign if the parent commit in the base repo is signed. | ||
* `headsigned`: Only sign if the head commit in the head branch is signed. | ||
* `commitssigned`: Only sign if all the commits in the head branch to the merge point are signed. | ||
* `always`: Always sign | ||
|
||
Options other than `never` and `always` can be combined as a comma | ||
separated list. | ||
|
||
## Installing and generating a GPG key for Gitea | ||
|
||
It is up to a server administrator to determine how best to install | ||
a signing key. Gitea generates all its commits using the server `git` | ||
command at present - and therefore the server `gpg` will be used for | ||
signing (if configured.) Administrators should review best-practices | ||
for gpg - in particular it is probably advisable to only install a | ||
signing secret subkey without the master signing and certifying secret | ||
key. | ||
|
||
## Obtaining the Public Key of the Signing Key | ||
|
||
The public key used to sign Gitea's commits can be obtained from the API at: | ||
|
||
```/api/v1/signing-key.gpg``` | ||
|
||
In cases where there is a repository specific key this can be obtained from: | ||
|
||
```/api/v1/repos/:username/:reponame/signing-key.gpg``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.