| Summary: | sandbox doesn't do anything in portage 2.0.21 | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Dan Armak (RETIRED) <danarmak> |
| Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | danarmak |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
OK, fixed in 2.0.22; also, sandbox will now protect against things in the root ebuild, not just stuff in functions. |
<danarmak> drobbins: oh right, i wanted to tell you. sandbox doesn't seem to work at all here, ever. i just put "touch /foobar" in an ebuild's main secion and it works, no acces denyings <drobbins> danarmak: try to find out why... <drobbins> danarmak: if /etc/ld.so.preload exists, etc. <danarmak> no it doesn't exist while ebuild is running <drobbins> danarmak: do this # python >>> import portage >>> portage.settings["FEATURES"] <danarmak> output: 'sandbox digest noauto noclean ccache' <drobbins> ok, then file a bug report. I'll see if I can replicate it here. it's possible that by removing some of azarah's patch, it got messed up