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

fix: always disable setuid sandbox on linux #15722

Merged
merged 1 commit into from Nov 15, 2018

Conversation

nornagon
Copy link
Member

Description of Change

Previously, when --enable-mixed-sandbox was passed, the setuid sandbox would not be disabled. In other places in the code we assume that the setuid sandbox is not in use.

Checklist

Release Notes

Notes: fix an issue where on Linux, the setuid sandbox was incorrectly enabled when passing --enable-mixed-sandbox

@nornagon nornagon requested review from zcbenz and a team November 14, 2018 21:38
@nornagon nornagon force-pushed the always-disable-setuid-sandbox branch from d42ee54 to 34de1a5 Compare November 14, 2018 23:11
Copy link
Member

@codebytere codebytere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this nukes the need for the upstream, yeah?

@nornagon
Copy link
Member Author

for upstream what?

@nornagon
Copy link
Member Author

Merging because mac CI is broken.

@nornagon nornagon merged commit 20116d7 into master Nov 15, 2018
@release-clerk
Copy link

release-clerk bot commented Nov 15, 2018

Release Notes Persisted

fix an issue where on Linux, the setuid sandbox was incorrectly enabled when passing --enable-mixed-sandbox

@nornagon nornagon deleted the always-disable-setuid-sandbox branch November 15, 2018 21:28
neo291 pushed a commit to neo291/electron that referenced this pull request Nov 16, 2018
neo291 pushed a commit to neo291/electron that referenced this pull request Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants