| 1 |
Quoting Jakub Moc <jakub@g.o>: |
| 2 |
> Georgi Georgiev napsal(a): |
| 3 |
>> I looked at the diff and it replaces export SANDBOX_ON=0 with |
| 4 |
>> RESTRICT="sandbox". It seems that the problem is older than that |
| 5 |
>> revision. |
| 6 |
> |
| 7 |
> No, the gcl problem didn't exist until vapier "fixed" the ebuild. I |
| 8 |
> still fail to see why RESTRICT=sandbox is any better than the |
| 9 |
> undocumented `export SANDBOX_ON=0` hack (which basically shouldn't be |
| 10 |
> used anywhere in the tree anyway, ideally)... |
| 11 |
|
| 12 |
Alright, I don't know what the "problem" is in your opinion, but the |
| 13 |
way I see it is that the ebuild wants to touch stuff outside the |
| 14 |
sandbox and *that* is the problem. There were obviously two solutions, |
| 15 |
well, workarounds -- an undocumented variable and the RESTRICT. |
| 16 |
*Neither* one is better than the other. What vapier did was make the |
| 17 |
problem visible, which doesn't mean that he introduced it. |
| 18 |
|
| 19 |
Further, by adopting ACCEPT_RESTRICT, it would be possible to be able to say: |
| 20 |
ACCEPT_RESTRICT=-sandbox: Do not let any ebuild touch anything outside |
| 21 |
the sandbox. |
| 22 |
ACCEPT_RESTRICT=-userpriv: Do not let any ebuild run with elevated privileges. |
| 23 |
|
| 24 |
|
| 25 |
---------------------------------------------------------------- |
| 26 |
This message was sent using IMP, the Internet Messaging Program. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives