1. 28 Jan, 2019 4 commits
  2. 27 Jan, 2019 15 commits
  3. 26 Jan, 2019 6 commits
  4. 21 Jan, 2019 4 commits
    • Merge pull request #2794 from brauner/2019-01-21/revert_seccomp_fuckup · 5283a118
      Wolfgang Bumiller authored
      Revert "seccomp: add rules for specified architecture only"
    • Revert "seccomp: add rules for specified architecture only" · 3e9671a1
      Christian Brauner authored
      This reverts commit f1bcfc79.
      
      The reverted branch breaks starting all seccomp confined containers. Not
      even a containers with our standard seccomp profile starts correctly.
      This is strong evidence that these changes have never been tested even
      with a standard workload. That is unacceptable!
      
      We are still happy to merge that feature but going forward we want tests
      that verify that standard workloads and new features work correctly.
      seccomp is a crucial part of our security story and I will not let the
      be compromised by missing tests!
      Signed-off-by: 's avatarChristian Brauner <christian.brauner@ubuntu.com>
    • Merge pull request #2786 from lifeng68/fix_seccomp · b6825c4b
      Christian Brauner authored
      seccomp: add rules for specified architecture only 
    • seccomp: add rules for specified architecture only · f1bcfc79
      LiFeng authored
      If the architecture is specified in the seccomp configuration, like:
      ```
      2
      whitelist errno 1
      [x86_64]
      accept allow
      accept4 allow
      ```
      We shoud add rules only for amd64 instead of add rules for
      x32/i386/amd64.
      
      1. If the [arch] was not specified in seccomp config, add seccomp rules
      for all all compat architectures.
      2. If the [arch] specified in seccomp config irrelevant to native host
      arch, the rules will be ignored.
      3. If specified [all] in seccomp config, add seccomp rules for all
      compat architectures.
      4. If specified [arch] as same as native host arch, add seccomp rules
      for the native host arch.
      5. If specified [arch] was not native host arch, but compat to host
      arch, add seccomp rules for the specified arch only, NOT add seccomp
      rules for native arch.
      Signed-off-by: 's avatarLiFeng <lifeng68@huawei.com>
  5. 18 Jan, 2019 4 commits
  6. 17 Jan, 2019 4 commits
  7. 16 Jan, 2019 1 commit
  8. 15 Jan, 2019 1 commit
  9. 11 Jan, 2019 1 commit