Re: [gentoo-dev] suggestion portage ebuild system file modification rights and protection

[Jan Krueger]

On Sunday 07 September 2003 18:21, Martin Schlemmer wrote:
> On Sun, 2003-09-07 at 22:18, Jan Krueger wrote:
> > On Sunday 07 September 2003 17:57, Martin Schlemmer wrote:
> > > and change '${D}/usr/sbin/foo' to '${D}/sbin/init' ?
> > > (ok, yes, its not going to work as a script if I remember
> > >  correctly .. but a simple c wrapper is quick to code).
> >
> > Cool, you just found another security bug in portage!
> >
> > go on :)
> >
> > So, the required feature thats implied with your detection, would be the
> > possibility to protect the already installed packages from modification
> > through installation of another package.
>
> And if this was baselayout that was compromised ?

Then you either
-should have audited the ebuild and code of baselayout
-hope that the md5sum protection alarmes you
-hope that the signature protection alarmes you (not yet implemented)
-hope that the security-oriented program analysis alarmes you (not yet 
implemented)
-hope that the problem hit someone else before you so it got widely published 
and you read the news
-hope that the automated test-procedures of gentoo detects the fault (not yet 
implemented)
-invent a special baselayout protection
-have a second authorized tree that got not compromised (because operational 
independend to the one gentoo tree with a special procedure that aims to 
prevent to move of compromised things between the trees) to compare against 
before emerge.
-install some other os (with maybe different problems)
-go out for a walk and watch sparrows or so :)
-forbid the emerge of baselayout because you think its better to install 
baselayout in a special hardened way instead.

i better stop now, it seems i could make this list very long :)

Jan


--
gentoo-dev@g.o mailing list