Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

doc

  • Clone with SSH
  • Clone with HTTPS
  • Jacob Vosmaer (GitLab)'s avatar
    Jacob Vosmaer (GitLab) authored
    Security and safety improvements for gitlab-workhorse integration
    
    Companion to https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/60
    
    - Use a custom content type when sending data to gitlab-workhorse
    - Verify (using JWT and a shared secret on disk) that internal API requests came from gitlab-workhorse
    
    This will allow us to build features in gitlab-workhorse that require
    more trust, and protect us against programming mistakes in the future.
    
    This is designed so that no action is required for installations from
    source. For omnibus-gitlab we need to add code that manages the shared
    secret.
    
    See merge request !5907
    b7e6da5a
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.