BigW Consortium Gitlab

  1. 29 Nov, 2017 1 commit
  2. 23 Nov, 2017 1 commit
  3. 17 Nov, 2017 1 commit
  4. 30 Oct, 2017 1 commit
  5. 23 Oct, 2017 1 commit
  6. 21 Oct, 2017 1 commit
  7. 19 Oct, 2017 1 commit
  8. 17 Oct, 2017 1 commit
  9. 16 Oct, 2017 1 commit
  10. 11 Sep, 2017 1 commit
  11. 09 Sep, 2017 1 commit
  12. 30 Aug, 2017 5 commits
    • More review comments · 29b40db5
      Nick Thomas authored
    • Address review comments · b84ca08e
      Nick Thomas authored
    • Rework the permissions model for SSH key restrictions · 68470602
      Nick Thomas authored
      `allowed_key_types` is removed and the `minimum_<type>_bits` fields are
      renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
      that the key type is disabled.
      
      This also feeds through to the UI - checkboxes per key type are out, inline
      selection of "forbidden" and "allowed" (i.e., no restrictions) are in.
      
      As with the previous model, unknown key types are disallowed, even if the
      underlying ssh daemon happens to support them. The defaults have also been
      changed from the lowest known bit size to "no restriction". So if someone
      does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
      least until the administrator restricts them.
    • Add settings for minimum key strength and allowed key type · b0f982fb
      Nick Thomas authored
      This is an amalgamation of:
      
      * Cory Hinshaw: Initial implementation !5552
      * Rémy Coutable: Updates !9350
      * Nick Thomas: Resolve conflicts and add ED25519 support !13712
  13. 11 Aug, 2017 1 commit
  14. 27 Jul, 2017 1 commit
  15. 13 Jul, 2017 1 commit
    • Fixes needed when GitLab sign-in is not enabled · 672a68d3
      Robin Bobbitt authored
      When sign-in is disabled:
       - skip password expiration checks
       - prevent password reset requests
       - don’t show Password tab in User Settings
       - don’t allow login with username/password for Git over HTTP requests
       - render 404 on requests to Profiles::PasswordsController
  16. 10 Jul, 2017 1 commit
  17. 07 Jul, 2017 1 commit
  18. 06 Jul, 2017 2 commits
  19. 14 Jun, 2017 1 commit
  20. 06 Jun, 2017 1 commit
  21. 05 Jun, 2017 1 commit
  22. 02 Jun, 2017 1 commit
  23. 31 May, 2017 1 commit
  24. 11 May, 2017 1 commit
    • Allow disabling usage ping in `gitlab.yml` · 3c546acf
      Sean McGivern authored
      Setting `usage_ping_enabled` to false in `gitlab.yml`:
      
      1. Disables the usage ping, regardless of the value stored in the database.
      2. Prevents the usage ping from being enabled through the admin panel. It can
         only be enabled by either removing the line from `gitlab.yml` and configuring
         through the admin panel, or setting it to true in `gitlab.yml`.
  25. 28 Apr, 2017 1 commit
  26. 26 Apr, 2017 1 commit
  27. 14 Apr, 2017 1 commit
  28. 03 Apr, 2017 1 commit
  29. 22 Mar, 2017 1 commit
  30. 18 Mar, 2017 1 commit
    • Fix Error 500 when application settings are saved · 681af5bc
      Stan Hu authored
      Due to a Rails bug, fetching the application settings from Redis
      may prevent the attribute methods from being loaded for the `ApplicationSetting`
      model. More details here: https://github.com/rails/rails/issues/27348
      
      There was also a secondary problem introduced by overriding these
      association methods which caused all default visibility levels to be
      set to `nil`. Before, the previous implementation allowed the string
      "20" to be saved as an integer, while now a table lookup happens
      before that. We fix this by enforcing the integer value in the
      controller and default to PRIVATE.
      
      Closes #29674
  31. 06 Mar, 2017 2 commits
  32. 02 Mar, 2017 2 commits
  33. 24 Feb, 2017 1 commit