Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn off 'noexec' option by default for named volumes #6325

Merged
merged 1 commit into from
May 22, 2020

Conversation

mheon
Copy link
Member

@mheon mheon commented May 21, 2020

We previously enforced this for security reasons, but as Dan has explained on several occasions, it's not very valuable there (it's trivially easy to bypass) and it does seriously annoy folks trying to use named volumes. Flip the default from 'on' to 'off'.

This is a backport from the master branch to v1.9 branch.

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 21, 2020
@mheon
Copy link
Member Author

mheon commented May 21, 2020

Ed's 160-volumes test has leaked in, but I don't think adding extra testing here is a bad thing.

@mheon
Copy link
Member Author

mheon commented May 21, 2020

@TomSweeneyRedHat
Copy link
Member

LGTM assuming happy tests

@edsantiago
Copy link
Member

LGTM. Thank you for bringing in the (new) tests rather than skipping them.

@edsantiago
Copy link
Member

Grumble - maybe the tests weren't such a good idea. One of the failures is almost certainly due to the CapItAliZaTion changes. The other, a failing touch with userns=keep-id, I think I've seen before and is a bug in 1.9 that has since been fixed.

I'm OK if you want to just remove those failing tests.

@mheon mheon force-pushed the noexec_backport branch from 95083a2 to 031d412 Compare May 21, 2020 19:47
We previously enforced this for security reasons, but as Dan has
explained on several occasions, it's not very valuable there
(it's trivially easy to bypass) and it does seriously annoy folks
trying to use named volumes. Flip the default from 'on' to 'off'.

This is a backport from the master branch to v1.9 branch.

Signed-off-by: Matthew Heon <[email protected]>
@mheon mheon force-pushed the noexec_backport branch from 031d412 to 67812a5 Compare May 22, 2020 13:51
@baude
Copy link
Member

baude commented May 22, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 22, 2020
@baude
Copy link
Member

baude commented May 22, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 22, 2020
@mheon
Copy link
Member Author

mheon commented May 22, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 22, 2020
@openshift-merge-robot openshift-merge-robot merged commit d48a47a into containers:v1.9 May 22, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants