talyz 7a67a2d1a8 gitlab: Add patch for db_key_base length bug, fix descriptions ... The upstream recommended minimum length for db_key_base is 30 bytes, which our option descriptions repeated. Recently, however, upstream has, in many places, moved to using aes-256-gcm, which requires a key of exactly 32 bytes. To allow for shorter keys, the upstream code pads the key in some places. However, in many others, it just truncates the key if it's too long, leaving it too short if it was to begin with. This adds a patch that fixes this and updates the descriptions to recommend a key of at least 32 characters. See https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53602		2021-04-27 17:49:43 +02:00
..
gitaly	gitlab: 13.9.4 -> 13.10.2	2021-04-07 23:23:24 +02:00
gitlab-shell	gitlab-shell: 13.15.1 -> 13.17.0	2021-04-09 00:36:32 +02:00
gitlab-workhorse	gitlab: 13.9.4 -> 13.10.2	2021-04-07 23:23:24 +02:00
rubyEnv	gitlab: 13.9.4 -> 13.10.2	2021-04-07 23:23:24 +02:00
data.json	gitlab: add back GITLAB_WORKHORSE_VERSION	2021-04-08 09:56:05 +02:00
default.nix	gitlab: Add patch for db_key_base length bug, fix descriptions	2021-04-27 17:49:43 +02:00
fix-grpc-ar.patch
remove-hardcoded-locations.patch	nixos/gitlab: Switch from unicorn to puma	2021-02-24 18:31:30 +01:00
reset_token.rake
update.py	gitlab: add back GITLAB_WORKHORSE_VERSION	2021-04-08 09:56:05 +02:00
yarnPkgs.nix	gitlab: 13.9.4 -> 13.10.2	2021-04-07 23:23:24 +02:00