Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-10-21 | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | |
2020-08-20 | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-29 | Add latest changes from gitlab-org/security/gitlab@13-1-stable-ee | GitLab Bot | |
2020-06-23 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-05-20 | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | |
2020-04-20 | Add latest changes from gitlab-org/gitlab@12-10-stable-ee | GitLab Bot | |
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-26 | Merge branch 'security-dns-rebind-ssrf-in-slack-notifications-ce' into 'master' | GitLab Release Tools Bot | |
Use Gitlab::HTTP for all chat notifications See merge request gitlab/gitlabhq!3517 | |||
2019-11-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-21 | Use Gitlab::HTTP for all chat notifications | Hordur Freyr Yngvason | |
2019-11-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-08-30 | Merge branch 'security-enable-image-proxy' into 'master' | GitLab Release Tools Bot | |
Use image proxy to mitigate stealing ip addresses Closes #2812 See merge request gitlab/gitlabhq!2926 | |||
2019-08-30 | Merge branch 'security-ssrf-kubernetes-dns-12-3' into 'master' | GitLab Release Tools Bot | |
DNS Rebind SSRF in Kubernetes Integration See merge request gitlab/gitlabhq!3345 | |||
2019-08-24 | Add support for using a Camo proxy server | Brett Walker | |
User images and videos will get proxied through the Camo server in order to keep malicious sites from collecting the IP address of users. | |||
2019-08-21 | Column was renamed in 12.2 | Thong Kuah | |
2019-08-21 | Override hostname when connecting via Kubeclient | Thong Kuah | |
Kubeclient uses rest-client. We hack into to access the net/http object so that we can patch to connect to the resolved IP + set hostname_override. Add specs for discord. The discord integration also uses rest-client, so since we patched rest-client, spec that the DNS rebinding protection works | |||
2019-08-20 | feat: SMIME signed notification emails | Diego Louzán | |
- Add mail interceptor the signs outgoing email with SMIME - Add lib and helpers to work with SMIME data - New configuration params for setting up SMIME key and cert files | |||
2019-06-28 | Remove ignored circuit_breaker columns | Zeger-Jan van de Weg | |
The circuit breaker itself got removed a while ago, when that happened some parts got left behind. Using grep old stale settings and validations were found and are now removed. | |||
2019-05-28 | Store Let's Encrypt private key in settings | Vladimir Shushlin | |
Storing this key in secrets.yml was a bad idea, it would require users using HA setups to manually replicate secrets across nodes during update, it also needed support from omnibus package * Revert "Generate Let's Encrypt private key" This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976. * Add Let's Encrypt private key to settings as encrypted attribute * Generate Let's Encrypt private key in database migration | |||
2019-05-09 | Generate Let's Encrypt private key | Vladimir Shushlin | |
2019-05-05 | Run rubocop -a on CE files | Stan Hu | |
2018-12-27 | Support both 0 and NULL lock_versions | Douwe Maan | |
2018-12-20 | Always load the metrics the last | Lin Jen-Shin | |
Because this could potentially load a model and we shouldn't load models before all the patches we have in places. | |||
2018-12-19 | Update specs to rails5 format | blackst0ne | |
Updates specs to use new rails5 format. The old format: `get :show, { some: params }, { some: headers }` The new format: `get :show, params: { some: params }, headers: { some: headers }` | |||
2018-12-06 | Revert "Prefer to use correlation-id in logs" | Kamil Trzciński | |
This reverts commit 3560b11922fd180eea5cafd0e763e0e601c5c4ee. | |||
2018-12-06 | Prefer to use correlation-id in logs | Kamil Trzciński | |
This changes `correlation_id` to be `correlation-id` when passed via jobs | |||
2018-12-06 | Log and pass correlation-id between Unicorn, Sidekiq and Gitaly | Kamil Trzciński | |
The Correlation ID is taken or generated from received X-Request-ID. Then it is being passed to all executed services (sidekiq workers or gitaly calls). The Correlation ID is logged in all structured logs as `correlation_id`. | |||
2018-11-27 | Correctly handle data-loss scenarios when encrypting columns | Nick Thomas | |
If the EncryptColumns background migration runs in a sidekiq with a stale view of the database schema, or when the purported destination columns don't actually exist, data loss can result. Attempt to work around these issues by reloading schema information before running the migration, and raising errors if the model reports that any of its source or destination columns are missing. | |||
2018-11-21 | Eliminate duplicated words | Takuya Noguchi | |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com> | |||
2018-06-27 | Migrate storage nesting check to Gitaly | Jacob Vosmaer (GitLab) | |
2018-06-05 | Fix Fog mocking | Kamil Trzciński | |