public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Environment Whitelisting
Date: Mon, 22 Aug 2005 23:52:11 +0900	[thread overview]
Message-ID: <200508222352.13913.jstubbs@gentoo.org> (raw)
In-Reply-To: <20050822035207.GA26017@phaenix.haell.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

On Monday 22 August 2005 12:52, Drake Wyrm wrote:
> Alec Warner <warnera6@egr.msu.edu> wrote:
> > Was talking with Brian about the build environment and how settings
> > were to be passed into the build environment.
> >
> > Essentially three scenarios were presented.
>
> Snip and summary:
>
> 1) Pass everything
>
> 2) Blacklist and strip bad stuff
>
> 3) Whitelist good stuff; strip everything else
>
> > To me 1) is unacceptable and 3) is the best option.  Feel free to
> > shoot these down as you see fit ;)
>
> Option 4: Strip everything.
>
> Nothing is passed from the original environment; everything passed in the
> environment is considered to be a "portage variable". This, I suppose,
> is an extreme case of the whitelist.

Well, I'll go against the flow. ;)

My preference would go 4, 3, 2 then 1. While Makefiles and configure scripts 
may be "broken" upstream, how long is it before the breakage goes 
unnoticed? More importantly, what's the chances of a dev finding the 
breakage before users? Cleansing the environment to me is akin to using 
sandbox. It offers protection against misbehaving packages...

-- 
Jason Stubbs

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-08-22 14:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 20:25 [gentoo-portage-dev] Environment Whitelisting Alec Warner
2005-08-22  1:24 ` Zac Medico
2005-08-22  3:52 ` [gentoo-portage-dev] " Drake Wyrm
2005-08-22  4:41   ` Zac Medico
2005-08-22 16:29     ` Kristian Benoit
2005-08-22 14:52   ` Jason Stubbs [this message]
2005-08-22 18:08     ` Zac Medico
2005-08-22 19:15       ` warnera6
2005-08-22 19:24         ` Zac Medico
2005-08-22 20:58           ` Brian Harring
2005-08-23  1:57           ` Kristian Benoit
2005-08-23  2:15             ` Brian Harring
2005-08-22 21:33 ` [gentoo-portage-dev] " Marius Mauch
2005-08-22 21:40   ` Brian Harring
2005-08-22 21:55     ` warnera6
2005-08-22 21:59     ` Marius Mauch
2005-08-22 22:19       ` Brian Harring
2005-08-22 22:36         ` Alec Warner
2005-08-22 22:41           ` Brian Harring
2005-08-22 23:01             ` [gentoo-portage-dev] Profiles [ was Environmental Whitelisting ] Alec Warner
2005-08-22 23:28     ` [gentoo-portage-dev] Environment Whitelisting Jason Stubbs
2005-08-22 23:56       ` Brian Harring
2005-08-23 10:50         ` Jason Stubbs
2005-08-23  0:27       ` Alec Warner
2005-08-23  2:46       ` Kristian Benoit
2005-08-23  3:40         ` Alec Warner
2005-08-23 16:19           ` Kristian Benoit

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=200508222352.13913.jstubbs@gentoo.org \
    --to=jstubbs@gentoo.org \
    --cc=gentoo-portage-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