All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Trentalancia <guido@trentalancia.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: eparis@redhat.com, selinux@tycho.nsa.gov
Subject: Re: [PATCH 33/67] policycoreutils: sandbox: FIXME rewrite /tmp handling
Date: Fri, 16 Sep 2011 08:10:43 +0200	[thread overview]
Message-ID: <1316153443.2364.48.camel@vortex> (raw)
In-Reply-To: <4E725512.4080206@redhat.com>

On Thu, 2011-09-15 at 15:42 -0400, Daniel J Walsh wrote:
> From 54ed5929b8f8ffac7bdc48d589c5cb38f6798530 Mon Sep 17 00:00:00 2001
> From: Eric Paris <eparis@redhat.com>
> Date: Mon, 15 Aug 2011 19:58:08 -0400
> Subject: [PATCH 33/67] policycoreutils: sandbox: FIXME rewrite /tmp
> handling
> 
> seunshare now creates a runtime temporary directory owned by root and
> with the sticky bit set properly.  Files from the user-specified
> directory
> are copied to the runtime directory and the changes synced back (using
> rsync)
> at the end of the seunshare run.
> 
> review needed to changelog correctness/completeness
> 
> Signed-off-by: Eric Paris <eparis@redhat.com>
> Acked-by: Dan Walsh <dwalsh@redhat.com>
> ---
>  policycoreutils/sandbox/sandbox     |    8 +-
>  policycoreutils/sandbox/seunshare.8 |    2 +-
>  policycoreutils/sandbox/seunshare.c |  488
> +++++++++++++++++++++++++++--------
>  3 files changed, 386 insertions(+), 112 deletions(-)

Is the above perhaps meant to fix CVE-2011-1011 ?


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2011-09-16  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 19:42 [PATCH 33/67] policycoreutils: sandbox: FIXME rewrite /tmp handling Daniel J Walsh
2011-09-16  6:10 ` Guido Trentalancia [this message]
2011-09-16 14:27   ` Daniel J Walsh

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=1316153443.2364.48.camel@vortex \
    --to=guido@trentalancia.com \
    --cc=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.