I noticed that #59 is not in the current (v1.3.0) release, which means that projects using go mod will not automatically get that fix, which is an additional fix to CVE-2019-16884;
changes since v1.3.0: v1.3.0...0089225
Would it be possible to tag a new release? Following SemVer, v1.3.1 is probably most appropriate.
note that runc v1.0.0-rc10 currently vendors 5215b18, so it could be considered to either tag that commit, or to tag current master (which has one additional, but probably minor change: #60)
ping @rhatdan @cyphar @mrunalp PTAL 🤗
I noticed that #59 is not in the current (v1.3.0) release, which means that projects using
go modwill not automatically get that fix, which is an additional fix to CVE-2019-16884;changes since v1.3.0: v1.3.0...0089225
Would it be possible to tag a new release? Following SemVer, v1.3.1 is probably most appropriate.
note that runc v1.0.0-rc10 currently vendors 5215b18, so it could be considered to either tag that commit, or to tag current master (which has one additional, but probably minor change: #60)
ping @rhatdan @cyphar @mrunalp PTAL 🤗