@@ -6,6 +6,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6
6
7
7
## [ Unreleased]
8
8
9
+ ## [ 1.2.0] - 2024-10-22
10
+
11
+ > できるときにできることをやるんだ。それが今だ。
12
+
13
+ ### Added
14
+ * In order to alleviate the remaining concerns around the memory usage and
15
+ (arguably somewhat unimportant, but measurable) performance overhead of
16
+ memfds for cloning ` /proc/self/exe ` , we have added a new protection using
17
+ ` overlayfs ` that is used if you have enough privileges and the running
18
+ kernel supports it. It has effectively no performance nor memory overhead
19
+ (compared to no cloning at all). (#4448 )
20
+
21
+ ### Fixed
22
+ * The original fix for [ CVE-2024 -45310] [ cve-2024-45310 ] was intentionally very
23
+ limited in scope to make it easier to review, however it also did not handle
24
+ all possible ` os.MkdirAll ` cases and thus could lead to regressions. We have
25
+ switched to the more complete implementation in the newer versions of
26
+ ` github.com/cyphar/filepath-securejoin ` . (#4393 , #4400 , #4421 , #4430 )
27
+ * In certain situations (a system with lots of mounts or racing mounts) we
28
+ could accidentally end up leaking mounts from the container into the host.
29
+ This has been fixed. (#4417 )
30
+ * The fallback logic for ` O_TMPFILE ` clones of ` /proc/self/exe ` had a minor
31
+ bug that would cause us to miss non-` noexec ` directories and thus fail to
32
+ start containers on some systems. (#4444 )
33
+ * Sometimes the cloned ` /proc/self/exe ` file descriptor could be placed in a
34
+ way that it would get clobbered by the Go runtime. We had a fix for this
35
+ already but it turns out it could still break in rare circumstances, but it
36
+ has now been fixed. (#4294 , #4452 )
37
+
38
+ ### Changed
39
+ * It is not possible for ` runc kill ` to work properly in some specific
40
+ configurations (such as rootless containers with no cgroups and a shared pid
41
+ namespace). We now output a warning for such configurations. (#4398 )
42
+ * memfd-bind: update the documentation and make path handling with the systemd
43
+ unit more idiomatic. (#4428 )
44
+ * We now use v0.16 of Cilium's eBPF library, including fixes that quite a few
45
+ downstreams asked for. (#4397 , #4396 )
46
+ * Some internal ` runc init ` synchronisation that was no longer necessary (due
47
+ to the ` /proc/self/exe ` cloning move to Go) was removed. (#4441 )
48
+
49
+ [ cve-2024-45310 ] : https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv
50
+
9
51
## [ 1.2.0-rc.3] - 2024-09-02
10
52
11
53
> The supreme happiness of life is the conviction that we are loved.
@@ -16,8 +58,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
16
58
maliciously configured containers to create empty files and directories on
17
59
the host.
18
60
19
- [ cve-2024-45310 ] : https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv
20
-
21
61
### Added
22
62
23
63
* Document build prerequisites for different platforms. (#4353 )
@@ -41,6 +81,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
41
81
* Makefile: Don't read COMMIT, BUILDTAGS, ` EXTRA_BUILDTAGS ` from env vars.
42
82
(#4380 )
43
83
84
+ [ cve-2024-45310 ] : https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv
85
+
44
86
## [ 1.2.0-rc.2] - 2024-06-26
45
87
46
88
> TRUE or FALSE, it's a problem!
@@ -802,7 +844,8 @@ implementation (libcontainer) is *not* covered by this policy.
802
844
cgroups at all during ` runc update ` ). (#2994 )
803
845
804
846
<!-- minor releases -->
805
- [ Unreleased ] : https://github.com/opencontainers/runc/compare/v1.2.0-rc.3...HEAD
847
+ [ Unreleased ] : https://github.com/opencontainers/runc/compare/v1.2.0...HEAD
848
+ [ 1.2.0 ] : https://github.com/opencontainers/runc/compare/v1.2.0-rc.1...v1.2.0
806
849
[ 1.1.0 ] : https://github.com/opencontainers/runc/compare/v1.1.0-rc.1...v1.1.0
807
850
[ 1.0.0 ] : https://github.com/opencontainers/runc/releases/tag/v1.0.0
808
851
@@ -831,6 +874,7 @@ implementation (libcontainer) is *not* covered by this policy.
831
874
[ 1.1.0-rc.1 ] : https://github.com/opencontainers/runc/compare/v1.0.0...v1.1.0-rc.1
832
875
833
876
<!-- 1.2.z patch releases -->
877
+ [ Unreleased 1.2.z ] : https://github.com/opencontainers/runc/compare/v1.2.0...release-1.2
834
878
[ 1.2.0-rc.3 ] : https://github.com/opencontainers/runc/compare/v1.2.0-rc.2...v1.2.0-rc.3
835
879
[ 1.2.0-rc.2 ] : https://github.com/opencontainers/runc/compare/v1.2.0-rc.1...v1.2.0-rc.2
836
880
[ 1.2.0-rc.1 ] : https://github.com/opencontainers/runc/compare/v1.1.0...v1.2.0-rc.1
0 commit comments