File _patchinfo of Package patchinfo

<patchinfo incident="9635">
  <issue tracker="bnc" id="1118897">VUL-0: CVE-2018-16873: go: cmd/go: remote command execution</issue>
  <issue tracker="bnc" id="1118899">VUL-0: CVE-2018-16875: go: crypto/x509: CPU denial of service</issue>
  <issue tracker="bnc" id="1118898">VUL-0: CVE-2018-16874: go: cmd/go: directory traversal</issue>
  <issue tracker="bnc" id="1095817">containers packages fail randomly due to %check</issue>
  <issue tracker="bnc" id="1121967">VUL-0: CVE-2019-5736: docker-runc: container breakout vulnerability</issue>
  <issue tracker="cve" id="2018-16873"/>
  <issue tracker="cve" id="2018-16875"/>
  <issue tracker="cve" id="2018-16874"/>
  <issue tracker="cve" id="2019-5736"/>
  <category>security</category>
  <rating>important</rating>
  <packager>cyphar</packager>
  <description>This update for runc fixes the following issues:

Security vulnerablities addressed:

- CVE-2019-5736: Effectively copying /proc/self/exe during re-exec to avoid
  write attacks to the host runc binary, which could lead to a container
  breakout (bsc#1121967)
- CVE-2018-16873: Fix a remote command execution during "go get -u"
  (boo#1118897)
- CVE-2018-16874: Fix a directory traversal in "go get" via curly braces in
  import paths (boo#1118898)
- CVE-2018-16875: Fix a CPU denial of service issue (boo#1118899)

Other changes and bug fixes:

- Update go requirements to &gt;= go1.10
- Create a symlink in /usr/bin/runc to enable rootless Podman and Buildah.
- Make use of %license macro
- Remove 'go test' from %check section, as it has only ever caused us problems
  and hasn't (as far as I remember) ever caught a release-blocking issue. Smoke
  testing has been far more useful. (boo#1095817)
- Upgrade to runc v1.0.0~rc6. Upstream changelog is available from
  https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc6
</description>
  <summary>Security update for runc</summary>
</patchinfo>