public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Buchholz <rbu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] EAPI change: Call ebuild functions from trusted working directory
Date: Thu, 9 Oct 2008 21:03:29 +0200	[thread overview]
Message-ID: <200810092103.33472.rbu@gentoo.org> (raw)

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

Hello,

currently, PMS section 10.1 states:

  Some functions may assume that their initial working directory is
  set to a particular location; these are noted below.
  If no initial working directory is mandated, it may be set to
  anything and the ebuild must not rely upon a particular location
  for it.

Please consider the following addition to this paragraph:

  The ebuild can rely that the chosen initial working direcotry is
  a trusted location that is not world-writable and owned by
  a privileged user and group.

This change affects all pkg_ functions.

Rationale:
This feature presents a security hardening to work around 
vulnerabilities in ebuilds and applications called by ebuilds, and the 
Gentoo Security Team considers this the official solution to
bug 239560 / GLSA 200810-02.

I would like:
 * everyone to comment on the change and propose changes to the wording
 * council to vote on this change to EAPI-0, -1 and -2.

Portage implements this in 2.1.4.5 and 2.2_rc12, Paludis in 0.30.2.
I have not heard back from Brian on pkgcore (because this issue has been 
disclosed to him on a really short notice).

Thanks,
Robert

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

             reply	other threads:[~2008-10-09 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 19:03 Robert Buchholz [this message]
2008-10-13 17:42 ` [gentoo-dev] EAPI change: Call ebuild functions from trusted working directory Donnie Berkholz
2008-10-13 18:20   ` Wulf C. Krueger
2008-10-13 18:56     ` Donnie Berkholz
2008-10-13 18:28   ` Ciaran McCreesh
2008-10-17  0:41     ` Robert Buchholz
2008-10-24 11:36       ` Robert Buchholz

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=200810092103.33472.rbu@gentoo.org \
    --to=rbu@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