-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
features: implement returning potentiallyUnsafeConfigAnnotations list #4217
Conversation
See https://github.com/opencontainers/runtime-spec/blob/v1.2.0/features.md#unsafe-annotations-in-configjson Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -64,6 +64,11 @@ var featuresCommand = cli.Command{ | |||
}, | |||
}, | |||
}, | |||
PotentiallyUnsafeConfigAnnotations: []string{ | |||
"bundle", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I totally forgot about this internal annotation. We should probably see if we can remove it...
(I suspect we also always override it, so it's technically not unsafe but it's better to be safe than sorry.)
ping @opencontainers/runc-maintainers |
Could this fix get backported to 1.1.x so security minded users aren't force to use a release candidate? |
For runc v1.1 we do not plan to bump up the spec version, so I'd suggest to use a hard-coded list |
Linking: This PR is misunderstood to fix the GHSA, but it actually does not, as the vuln is not on runc side. |
See https://github.com/opencontainers/runtime-spec/blob/v1.2.0/features.md#unsafe-annotations-in-configjson