From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Overlays and Metadata Cache
Date: Sun, 21 Jun 2009 11:09:40 -0700 [thread overview]
Message-ID: <4A3E7764.7040905@gentoo.org> (raw)
In-Reply-To: <200906211700.01677.patrick@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Patrick Lauer wrote:
>>> The metadata cache is "inert" in the sense that it isn't executable
>>> code (and if anyone tries to execute it ... "You're doing it wrong"
>>> comes to mind"), so adding it does not pessimize the situation.
>> But generating that cache means running code, and one of the things
>> that code could do is modify every overlay distributed by the box in
>> question such that anyone using any of those overlays will run
>> arbitrary code whenever they do emerge -p world.
>
> Good, this means we have to isolate it so that only each overlay itself exists
> in an environment that generates the metadata cache. A bit bothersome, but
> nothing more than adding a line or two to the script(s) that drive(s) this
> process.
If you generate a user with a separate uid for each overlay then
that will probably be provide a sufficient level of privilege isolation.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAko+d2MACgkQ/ejvha5XGaPzJQCeIg2d8MVhJTyhZWKCQGtZnY3V
Dk8An0f8WnJL/lb7iJZzlB+hxQDfNLTG
=pXrm
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-06-21 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 16:46 [gentoo-dev] [RFC] Overlays and Metadata Cache Patrick Lauer
2009-06-20 17:09 ` Fabian Groffen
2009-06-20 18:16 ` Zac Medico
2009-06-20 18:22 ` Ciaran McCreesh
2009-06-20 18:40 ` Patrick Lauer
2009-06-20 19:00 ` Ciaran McCreesh
2009-06-21 8:43 ` Patrick Lauer
2009-06-21 14:26 ` Ciaran McCreesh
2009-06-21 15:00 ` Patrick Lauer
2009-06-21 15:20 ` Ciaran McCreesh
2009-06-21 18:09 ` Zac Medico [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3E7764.7040905@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox