Skip to content
Snippets Groups Projects
  1. Apr 12, 2022
  2. Apr 11, 2022
    • Stan Hu's avatar
      ruby: Enable OPENSSL_FIPS macro for system SSL builds · 7f6ff530c9f7
      Stan Hu authored
      In the Ubuntu 18.04 FIPS builds, currently `OpenSSL.fips_mode` is
      `false`, which prevents GitLab from entering FIPS mode.
      
      Even though these builds properly link against the FIPS-enabled system
      OpenSSL, this flag is `false` because Ruby compiles out the dynamic
      `FIPS_mode()` checks (https://wiki.openssl.org/index.php/FIPS_mode())
      unless the `OPENSSL_FIPS` macro is defined. In RedHat, `OPENSSL_FIPS`
      is always defined in `/usr/include/openssl/opensslconf-x86_64.h`, but
      this is not the case for Ubuntu. On non FIPS-systems, `FIPS_mode()`
      should return 0 (not available), so this compile-time guard should not
      be necessary. For now, we only enable it for builds that link
      against the system SSL.
      
      Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6775
      
      Changelog: fixed
      7f6ff530c9f7
  3. Apr 07, 2022
  4. Apr 06, 2022
  5. Apr 05, 2022
  6. Apr 04, 2022
  7. Apr 01, 2022
  8. Mar 10, 2022
  9. Apr 01, 2022
    • Balasankar 'Balu' C's avatar
      Merge branch 'pks-gitaly-runtime-dir' into 'master' · 33607e79255e
      Balasankar 'Balu' C authored
      gitaly: Introduce new `runtime_dir` configuration
      
      Closes #6755
      
      See merge request gitlab-org/omnibus-gitlab!5999
      33607e79255e
    • Patrick Steinhardt's avatar
      gitaly: Set up newly introduced runtime directory · 66063e3ffb8c
      Patrick Steinhardt authored
      Gitaly has recently introduced support for a new runtime directory: this
      directory is supposed to hold all files and directories Gitaly needs to
      create at runtime in order to operate correctly. Most importantly, this
      includes things like internal sockets, the Git execution environment and
      the temporary hooks directory. The intent is for there to finally be a
      unified approach to handle this kind of data in a central place.
      
      As part of this Gitaly has introduced a new `runtime_dir` configuration
      that allows the admin to choose where that directory should be located.
      If left unset, Gitaly simply uses the global temporary directory, which
      is typicall `/tmp`. There are systems though where files in there will
      automatically get pruned in regular intervals if the files are older
      than a specific grace period and not used. Whether a directory is used
      or not is based on the atime though, which may not even be updated in
      case `/tmp` is mounted with `noatime`. Consequentially, it could happen
      that Gitaly's runtime files are pruned even though they're still in use.
      
      Wire up support for this new runtime directory and set up a default
      value so that we don't fall prey to this issue.
      
      Changelog: changed
      66063e3ffb8c
  10. Mar 31, 2022
  11. Mar 30, 2022
  12. Mar 29, 2022
  13. Mar 28, 2022
Loading