-
Notifications
You must be signed in to change notification settings - Fork 569
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
Limit the memory size used by the jailed process #593
Comments
|
On Fri, 2016-06-24 at 10:02 -0700, Reiner Herrmann wrote:
I am aware about ulimit, but this will be probably a little more |
It's probably a bit more convenient, I agree, but duplicating functionality already provided by other means also increases the complexity of firejail. |
Another way is to assign the process to a cgroup and set limits on the cgroup (which you might be able to do in a config file somewhere). |
Yes, cgroup is the way to go. Set up a control group and pass it to the sandbox using --cgroup. |
We need to limit the memory size used by the jailed process, so that a hacked would not run out of memory and swap.
The text was updated successfully, but these errors were encountered: