- 29 11月, 2019 2 次提交
-
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
- 28 11月, 2019 6 次提交
-
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
- 27 11月, 2019 24 次提交
-
-
由 GitLab Bot 提交于
-
由 Alessio Caiazza 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Release Tools Bot 提交于
[ci skip]
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-
由 GitLab Release Tools Bot 提交于
[ci skip]
-
由 GitLab Release Tools Bot 提交于
Update Workhorse and Gitaly to fix a security issue See merge request gitlab/gitlabhq!3499
-
由 GitLab Release Tools Bot 提交于
Escape namespace in label references Closes #2941 See merge request gitlab/gitlabhq!3509
-
由 GitLab Release Tools Bot 提交于
Use Gitlab::HTTP for all chat notifications See merge request gitlab/gitlabhq!3517
-
由 GitLab Release Tools Bot 提交于
GitLab stores AWS, Slack, Askimet, reCaptcha tokens in plaintext See merge request gitlab/gitlabhq!3518
-
由 GitLab Release Tools Bot 提交于
Prevent guests from seeing commits for cycle analytics See merge request gitlab/gitlabhq!3519
-
由 GitLab Release Tools Bot 提交于
Fix private comment Elasticsearch leak See merge request gitlab/gitlabhq!3521
-
由 GitLab Release Tools Bot 提交于
Hide AWS secret on Admin Integration page See merge request gitlab/gitlabhq!3525
-
由 Justin Ho Tuan Duong 提交于
-
由 GitLab Release Tools Bot 提交于
Related Branches Visible to Guests in Issue Activity See merge request gitlab/gitlabhq!3537
-
由 GitLab Release Tools Bot 提交于
Fix invalid byte sequence See merge request gitlab/gitlabhq!3545
-
由 GitLab Release Tools Bot 提交于
Check permissions before showing a forked project's source See merge request gitlab/gitlabhq!3554
-
由 GitLab Release Tools Bot 提交于
Ensure attributes that end in `_ids` are cleaned See merge request gitlab/gitlabhq!3561
-
由 GitLab Release Tools Bot 提交于
[ci skip]
-
- 26 11月, 2019 8 次提交
-
-
由 GitLab Bot 提交于
-
由 Arturo Herrero 提交于
We had concerns about the cached values on Redis with the previous two releases strategy: First release (this commit): - Create new encrypted fields in the database. - Start populating new encrypted fields, read the encrypted fields or fallback to the plaintext fields. - Backfill the data removing the plaintext fields to the encrypted fields. Second release: - Remove the virtual attribute (created in step 2). - Drop plaintext columns from the database (empty columns after step 3). We end up with a better strategy only using migration scripts in one release: - Pre-deployment migration: Add columns required for storing encrypted values. - Pre-deployment migration: Store the encrypted values in the new columns. - Post-deployment migration: Remove the old unencrypted columns
-
由 Arturo Herrero 提交于
This is the plan to encrypt the plaintext tokens: First release (this commit): 1. Create new encrypted fields in the database. 2. Start populating new encrypted fields, read the encrypted fields or fallback to the plaintext fields. 3. Backfill the data removing the plaintext fields to the encrypted fields. Second release: 4. Remove the virtual attribute (created in step 2). 5. Drop plaintext columns from the database (empty columns after step 3).
-
由 GitLab Bot 提交于
-
由 Imre Farkas 提交于
-
由 DJ Mountney 提交于
This prevents an issue where you can steal other projects objects by asking for ids that don't belong to you in import.
-
由 GitLab Bot 提交于
-
由 GitLab Bot 提交于
-