BigW Consortium Gitlab

  1. 04 Sep, 2017 1 commit
  2. 03 Sep, 2017 3 commits
  3. 01 Sep, 2017 1 commit
  4. 31 Aug, 2017 3 commits
    • `current_application_settings` belongs on `Gitlab::CurrentSettings` · 5883ce95
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
    • Don't show references to Pages when not available · 04cd47dd
      Zeger-Jan van de Weg authored
      In this instance its subgroups, and given we can't deploy it, we
      shouldn't allow it to be shown.
      
      Fixes gitlab-org/gitlab-ce#34864
  5. 30 Aug, 2017 6 commits
    • 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
    • Add check for access to Namespace · b9b0b37b
      Rubén Dávila authored
    • Fix MySQL failure for emoji autocomplete · 07a7801c
      Sean McGivern authored
      Postgres lets you treat `count` as another alias for `COUNT(*)` apparently, even
      if that's not the actual alias used.
    • Fix specs · a540f55c
      Douwe Maan authored
    • Add filter by my reaction · 7187395e
      Hiroyuki Sato authored
  6. 29 Aug, 2017 3 commits
  7. 28 Aug, 2017 3 commits
  8. 26 Aug, 2017 1 commit
  9. 24 Aug, 2017 2 commits
  10. 22 Aug, 2017 2 commits
  11. 21 Aug, 2017 1 commit
  12. 18 Aug, 2017 1 commit
  13. 17 Aug, 2017 6 commits
  14. 15 Aug, 2017 2 commits
  15. 14 Aug, 2017 2 commits
  16. 11 Aug, 2017 3 commits