summaryrefslogtreecommitdiff
path: root/app/models/hooks/web_hook.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-061-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-311-3/+15
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-161-6/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-131-48/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-01-251-40/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-01-101-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-12-011-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-11-281-10/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-11-241-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-11-221-12/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-11-101-1/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-281-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-211-4/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-201-2/+21
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-181-1/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-171-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-10-131-2/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-08-011-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-07-221-11/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-07-191-0/+9
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-07-151-0/+30
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-06-161-10/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-06-101-0/+25
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-06-071-0/+10
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-03-081-4/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-02-161-2/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-01-111-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-12-141-4/+28
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-09-101-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-07-281-4/+9
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-311-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-211-0/+9
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-201-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-141-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-061-2/+41
|
* Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-27476GitLab Bot2019-12-161-0/+4
|
* Add latest changes from gitlab-org/gitlab@masterlistGitLab Bot2019-10-171-1/+1
|
* Refactor SystemHookUrlValidator and specsGeorge Koltsov2019-08-021-2/+2
| | | | | | Simplify SystemHookUrlValidator to inherit from PublicUrlValidator Refactor specs to move out shared examples to be used in both system hooks and public url validators.
* Add outbound requests setting for system hooksGeorge Koltsov2019-08-021-1/+1
| | | | | | | This MR adds new application setting to network section `allow_local_requests_from_system_hooks`. Prior to this change system hooks were allowed to do local network requests by default and we are adding an ability for admins to control it.
* Inherit from ApplicationRecord instead of ActiveRecord::BaseNick Thomas2019-03-281-1/+1
|
* Use a 32-byte version of db_key_base for web hooksNick Thomas2018-12-051-2/+2
| | | | | | | | | | | | | | | | | AES-256-GCM cipher mode requires a key that is exactly 32 bytes long. We already handle the case when the key is too long, by truncating, but the key can also be too short in some installations. Switching to a key that is always exactly the right length (by virtue of right-padding ASCII 0 characters) allows encryption to proceed, without breaking backward compatibility. When the key is too short, encryption fails with an `ArgumentError`, causing the web hooks functionality to be unusable. As a result, zero rows can exist with values encrypted with the too-short key. When the key is too long, it is silently truncated. In this case, the key is unchanged, so values encrypted with the new too-long key will still be successfully decrypted.
* Remove unencrypted webhook token and URL columnsNick Thomas2018-10-091-34/+0
|
* Encrypt webhook tokens and URLs in the databaseNick Thomas2018-10-011-0/+44
|
* Disable existing offenses for the CodeReuse copsYorick Peterse2018-09-111-0/+4
| | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
* Filter project hooks by branchDuana Saskia2018-08-131-0/+1
| | | | | | Allow specificying a branch filter for a project hook and only trigger a project hook if either the branch filter is blank or the branch matches. Only supported for push_events for now.
* Enable more frozen string in app/models/**/*.rbgfyoung2018-08-071-0/+2
| | | | Partially addresses #47424.
* Add validation to webhook and service URLs to ensure they are not blocked ↵Francisco Javier López2018-06-011-1/+8
| | | | because of SSRF
* Merge branch ↵Robert Speicher2018-01-161-0/+1
| | | | | | | | | | | | '41293-fix-command-injection-vulnerability-on-system_hook_push-queue-through-web-hook' into 'security-10-3' Don't allow line breaks on HTTP headers See merge request gitlab/gitlabhq!2277 (cherry picked from commit 7fc0a6fc096768a5604d6dd24d7d952e53300c82) 073b8f9c Don't allow line breaks on HTTP headers
* Wrong data type when testing webhooksAlexander Randa2017-07-201-14/+0
|
* Added Cop to blacklist the use of `dependent:`Yorick Peterse2017-07-061-1/+1
| | | | | | | | This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).