summaryrefslogtreecommitdiff
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'backport-ee-2456' into 'master'Robert Speicher2017-07-273-4/+14
|\ | | | | | | | | Skip OAuth authorization for trusted applications See merge request !13061
| * Backport gitlab-ee!2456Oswaldo Ferreira2017-07-273-4/+14
| |
* | Merge branch 'feature/gpg-signed-commits' into 'master'Dmitriy Zaporozhets2017-07-2717-0/+1105
|\ \ | |/ |/| | | | | | | | | GPG signed commits Closes #20268 See merge request !9546
| * remove log statements from workersAlexis Reigel2017-07-272-21/+0
| |
| * improve gpg key validationAlexis Reigel2017-07-271-1/+9
| | | | | | | | | | | | | | | | when omitting the end part of the key ('-----END PGP PUBLIC KEY BLOCK-----') the error message was not about the key anymore, but about the missing fingerprint and primary_keyid, which was confusing for the user. the new validation checks that the end also matches the expected format.
| * optimize query, only select relevant db columnsAlexis Reigel2017-07-271-11/+53
| |
| * validate the foreign_key instead of the relationAlexis Reigel2017-07-271-1/+1
| |
| * simplify nil handlingAlexis Reigel2017-07-271-0/+4
| |
| * fetch gpg signature badges by ajaxAlexis Reigel2017-07-271-2/+2
| |
| * use short project path helpersAlexis Reigel2017-07-271-6/+6
| |
| * swap user's name and the user's usernameAlexis Reigel2017-07-271-1/+1
| |
| * show gpg key's user info when no profile existsAlexis Reigel2017-07-271-3/+20
| |
| * store gpg user name and email on the signatureAlexis Reigel2017-07-274-9/+45
| |
| * user may now revoke a gpg keyAlexis Reigel2017-07-272-0/+43
| | | | | | | | | | other than just removing a key, which doesn't affect the verified state of a commit, revoking a key unverifies all signed commits.
| * generate gpg signature on pushAlexis Reigel2017-07-272-0/+79
| |
| * improve spacing / alignments in gpg popupAlexis Reigel2017-07-271-7/+7
| |
| * extract common methodAlexis Reigel2017-07-271-8/+21
| |
| * also update gpg_signatures when gpg_key is nullAlexis Reigel2017-07-271-15/+55
| |
| * simplify fetching of commitAlexis Reigel2017-07-272-1/+14
| |
| * validate presence of user on gpg_keyAlexis Reigel2017-07-271-0/+1
| |
| * use hash instead of 2d arrayAlexis Reigel2017-07-271-4/+4
| |
| * use sign_in instead of login_withAlexis Reigel2017-07-271-3/+3
| |
| * remove the :gpg rspec tagAlexis Reigel2017-07-274-12/+12
| | | | | | | | | | since everything (except the CurrentKeyChain method) operates on a tempoary keychain anyway we don't need this anymore.
| * use updated gitlab-test repo for signed commitsAlexis Reigel2017-07-272-19/+6
| |
| * extract variableAlexis Reigel2017-07-271-6/+7
| |
| * add gpg commit popover badgesAlexis Reigel2017-07-271-0/+25
| |
| * perform signature update in sidekiq workerAlexis Reigel2017-07-272-4/+46
| |
| * update features specs for gpg commitsAlexis Reigel2017-07-271-13/+38
| |
| * need to wrap the raw commit in a commit modelAlexis Reigel2017-07-271-2/+7
| |
| * update invalid gpg signatures when email changesAlexis Reigel2017-07-272-25/+81
| |
| * update invalid gpg signatures when key is createdAlexis Reigel2017-07-272-0/+61
| |
| * memoize verified_signature callAlexis Reigel2017-07-271-6/+6
| |
| * store gpg_key_primary_keyid for unknown gpg keysAlexis Reigel2017-07-272-1/+2
| | | | | | | | | | we need to store the keyid to be able to update the signature later in case the missing key is added later.
| * move signature cache read to Gpg::CommitAlexis Reigel2017-07-272-94/+49
| | | | | | | | | | | | | | | | 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.
| * gpg signature is only valid when key is verifiedAlexis Reigel2017-07-272-2/+42
| |
| * bail if the commit has no signatureAlexis Reigel2017-07-271-0/+6
| |
| * cache the gpg commit signatureAlexis Reigel2017-07-272-23/+118
| | | | | | | | | | we store the result of the gpg commit verification in the db because the gpg verification is an expensive operation.
| * gpg signature model for gpg verification cachingAlexis Reigel2017-07-271-0/+14
| |
| * verify gpg commit using tmp keyring and db queryAlexis Reigel2017-07-272-2/+19
| |
| * add primary keyid attribute to gpg keysAlexis Reigel2017-07-274-6/+28
| |
| * don't sync to keychain fileAlexis Reigel2017-07-273-140/+8
| |
| * remove gpg from keychain when user's email changesAlexis Reigel2017-07-273-27/+89
| |
| * notification email on add new gpg keyAlexis Reigel2017-07-274-0/+57
| |
| * gpg email verificationAlexis Reigel2017-07-272-12/+53
| |
| * move current keychain methods to namespaceAlexis Reigel2017-07-272-20/+22
| |
| * email handling for gpg keysAlexis Reigel2017-07-271-0/+26
| |
| * test with a gpg key with multiple emailsAlexis Reigel2017-07-273-16/+21
| |
| * use example gpg key instead of my ownAlexis Reigel2017-07-274-211/+92
| |
| * feature spec for gpg signed commitsAlexis Reigel2017-07-271-0/+32
| |
| * add second gpg key for specsAlexis Reigel2017-07-275-223/+309
| |