An error occurred fetching the project authors.
- 17 Jun, 2019 1 commit
-
-
David Palubin authored
-
- 05 Dec, 2018 1 commit
-
-
Stan Hu authored
An unknown public GPG key will result in a GPGME::Error thrown from gpg, which would cause an Error 500 on the signatures endpoint. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54729
-
- 01 Mar, 2018 1 commit
-
-
Ahmad Sherif authored
Closes gitaly#1046
-
- 19 Feb, 2018 1 commit
-
-
Stan Hu authored
Closes gitlab-org/gitlab-ee#4825
-
- 18 Jan, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 05 Oct, 2017 1 commit
-
-
Rubén Dávila authored
-
- 05 Sep, 2017 4 commits
-
-
Alexis Reigel authored
-
Alexis Reigel authored
this is used to make a difference between a committer email that belongs to user, where the user used a different email for the gpg key. this means that the user is the same, but a different, unverified email is used for the signature.
-
Alexis Reigel authored
-
Alexis Reigel authored
the updated verification of a gpg signature requires the committer's email to also match the user's and the key's emails.
-
- 16 Aug, 2017 1 commit
-
-
Douwe Maan authored
-
- 27 Jul, 2017 8 commits
-
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
we need to store the keyid to be able to update the signature later in case the missing key is added later.
-
Alexis Reigel authored
as we write the cache in the gpg commit class already the read should also happen there. This also removes all logic from the main commit class, which just proxies the call to the Gpg::Commit now.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
we store the result of the gpg commit verification in the db because the gpg verification is an expensive operation.
-