-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Excessive permissions #298
Comments
Currently EMBA needs root privs for multiple extraction modules, as well as for the chroot environment from the user-mode emulator. |
What kind of extraction needs root ? If you need chroot there is no problem with launching chroot command itself with sudo, instead of running full framework full of uncertain tools as root. |
Keep calm guy ... if you ask you get the info.
On the other side you do not need to use it at all. For all that are interested the following modules currently need root privs:
Probably other modules also need root privs. I need to check this in detail. |
This issue is stale because it has been open for 28 days with no activity. |
This issue is stale because it has been open for 28 days with no activity. |
This issue is stale because it has been open for 28 days with no activity. |
This issue is stale because it has been open for 28 days with no activity. |
for sure its recommended to run nested vm's |
This issue is stale because it has been open for 28 days with no activity. |
How the #wontfix and #Research tags come all together, does it mean there is an intent to change current behaviour (ongoing work or PR accept) or not ? |
#research -> further research work needed to identify all the affected areas and start repairing them or find some solution If you would like to start digging into this issue you are welcome. We can use this issue for further discussions, as well as a dedicated disussion in the gh discussion area. |
This issue is stale because it has been open for 28 days with no activity. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
With docker enabled this script needs root privileges
Expected behavior
There is no reason software of this kind should need root privileges every time. Especially when most of work is done within containers
The text was updated successfully, but these errors were encountered: