An error occurred fetching the project authors.
  1. 04 Sep, 2019 1 commit
  2. 30 Apr, 2019 1 commit
  3. 13 Dec, 2018 2 commits
  4. 07 Sep, 2018 1 commit
  5. 15 Aug, 2018 2 commits
  6. 13 Aug, 2018 1 commit
  7. 31 Jul, 2018 1 commit
  8. 26 Jul, 2018 1 commit
    • Ævar Arnfjörð Bjarmason's avatar
      Add support for SSH certificate authentication · 2e8b6702
      Ævar Arnfjörð Bjarmason authored
      This along with the code submitted to gitlab-ce in the
      gitlab-org/gitlab-ce! MR implements SSH certificate
      authentication. See the docs added to gitlab-ce for why and how to
      enable this. This, along with that MR, closes
      gitlab-org/gitlab-ce#3457
      
      Implementation notes:
      
       - Because it's easy to do, and because an earlier nascent version of
         this would pass user-ID to gitlab-shell, that's now supported, even
         though the SSH certificate authentication uses username-USERNAME.
      
       - The astute reader will notice that not all the API calls in
         gitlab-ce's lib/api/internal.rb support a "username" argument, some
         only support "user_id".
      
         There's a few reasons for this:
      
           a) For this to be efficient, I am bending over backwards to avoid
              extra API calls when using SSH certificates.
      
              Therefore the /allowed API call will now return a "user id" to
              us if we're allowed to proceed further. This is then fed to
              existing APIs that would only be called after a successful
              call to /allowed.
      
           b) Not all of the git-shell codepaths go through
              /internal/allowed, or ever deal with a repository, e.g. the
              argument-less "Welcome to GitLab", and
              /internal/2fa_recovery_codes. These need to use
              /internal/discover to figure out details about the user, so
              support looking that up by username.
      
           c) Once we have the "user id", the GL_ID gets passed down to
              e.g. user-authored hooks. I don't want to have those all break
              by having to handle a third GL_ID mode of "username" in
              addition to the current "key id" and "user id".
      2e8b6702
  9. 20 Jul, 2018 1 commit
  10. 19 Mar, 2018 1 commit
  11. 28 Jun, 2017 2 commits
  12. 11 Oct, 2016 1 commit
  13. 10 Aug, 2016 4 commits
  14. 05 Aug, 2016 1 commit
  15. 03 Aug, 2016 1 commit
  16. 01 Aug, 2016 1 commit
  17. 16 Jul, 2015 1 commit
    • Jacob Vosmaer's avatar
      Remove keys from authorized_keys in-place · 4fd8e44b
      Jacob Vosmaer authored
      This will speed up the rm-key operation. The downside is that
      authorized_keys will not shrink when you remove a key. If this ever
      becomes a problem it can be fixed by running 'rake gitlab:shell:setup'.
      4fd8e44b
  18. 15 Oct, 2014 1 commit
    • David Martin's avatar
      Added list-keys command and spec · 89d8af46
      David Martin authored
      Removed puts and tidied up regex
      
      Address the hound
      
      Address the hound, again
      
      Use single quotes
      
      Add back travis.yml file
      
      Remove travis.yml, only keep on fh-master
      
      Use single quotes
      
      Use single quotes
      89d8af46
  19. 23 Jun, 2014 1 commit
  20. 31 May, 2014 1 commit
  21. 30 May, 2014 1 commit
  22. 18 Apr, 2014 1 commit
  23. 14 Mar, 2014 1 commit
  24. 25 Nov, 2013 1 commit
  25. 20 Nov, 2013 2 commits
  26. 05 Nov, 2013 1 commit
  27. 02 Nov, 2013 1 commit
  28. 31 Oct, 2013 1 commit
  29. 19 Jul, 2013 1 commit
    • Jacob Vosmaer's avatar
      Use Tempfile instead of `sed -i` · 4de0ee3b
      Jacob Vosmaer authored
      The syntax for `sed -i` is incompatible between GNU sed and
      BSD sed. By Tempfile from the Ruby standard library we can
      avoid using the `-i` option of sed.
      4de0ee3b
  30. 18 May, 2013 1 commit
  31. 17 May, 2013 1 commit
  32. 30 Apr, 2013 1 commit
  33. 11 Mar, 2013 1 commit