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.

Sign up for GitHub

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

Jump to bottom

CLONE_NEWUSER to avoid having a pool of UIDs ? #3

Closed
seirl opened this issue Aug 8, 2015 · 1 comment
Closed

CLONE_NEWUSER to avoid having a pool of UIDs ? #3

seirl opened this issue Aug 8, 2015 · 1 comment

Comments

@seirl
Copy link
Contributor

seirl commented Aug 8, 2015

Couldn't we avoid having a pool of UIDs, leading to potential races and adding constraints to the execution, by passing the CLONE_NEWUSER flag to clone(2) and always using the same uid and gid when dropping privileges?
If this change sounds good to you, I can work on it, it shouldn't take long!
@seirl
Copy link
Contributor Author

seirl commented Aug 8, 2015

Nevermind, after trying things out, I realized we'd need to keep a pool of uids somewhere to write the mapping in the procfs :/

@seirl seirl closed this as completed Aug 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seirl