| 1 |
On Sunday 07 September 2003 17:57, Martin Schlemmer wrote: |
| 2 |
> and change '${D}/usr/sbin/foo' to '${D}/sbin/init' ? |
| 3 |
> (ok, yes, its not going to work as a script if I remember |
| 4 |
> correctly .. but a simple c wrapper is quick to code). |
| 5 |
|
| 6 |
Cool, you just found another security bug in portage! |
| 7 |
|
| 8 |
go on :) |
| 9 |
|
| 10 |
So, the required feature thats implied with your detection, would be the |
| 11 |
possibility to protect the already installed packages from modification |
| 12 |
through installation of another package. |
| 13 |
|
| 14 |
Or said in different words: |
| 15 |
if one emerges an ebuild this ebuild is allowed only to add files to the |
| 16 |
system that did not exist before and/or change only files that got installed |
| 17 |
by a previous revision of the same ebuild. This way it would be impossible |
| 18 |
for the ebuild to change existing files, like /sbin/init, in the system. Its |
| 19 |
forbidden. |
| 20 |
|
| 21 |
Thank you for enlightening this. |
| 22 |
|
| 23 |
Some days ago i stumbled over this: |
| 24 |
try |
| 25 |
emerge ezmlm |
| 26 |
and |
| 27 |
emerge ezmlm-idx |
| 28 |
they happily overwrite each other. Preventing such mess inside portage would |
| 29 |
be of great value for security and overall quality. |
| 30 |
|
| 31 |
Jan |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives