All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: debian-devel@lists.debian.org,
	Scott James Remnant <scott@netsplit.com>,
	SE-Linux <selinux@tycho.nsa.gov>,
	Dpkg Development <debian-dpkg@lists.debian.org>
Subject: Re: dpkg and selinux
Date: Tue, 7 Sep 2004 13:39:31 +0100	[thread overview]
Message-ID: <20040907123930.GD17760@lkcl.net> (raw)
In-Reply-To: <200409072220.53751.russell@coker.com.au>

On Tue, Sep 07, 2004 at 10:20:53PM +1000, Russell Coker wrote:

> > > Vaguely, files are unpacked in a temporary place then moved into the
> > > right place (inside process_archive).
> >
> >  okay, then that means that:
> >
> >  1b) the move needs to be handled carefully to ensure that the
> >     selinux permissions are preserved
> 
> This is already catered for.  The only move which could lose the SE Linux 
> context is one that crosses file systems.  This doesn't work for package 
> installation anyway (imagine if /bin/bash or /usr/bin/perl was being replaced 
> and half way through copying over the new file there was a power failure).
 
 so... if i have /usr, /var, / and /boot on separate partitions, and move
 files around, is the selinux context lost or kept?





> >  2) the linux kernel could be "prepped" by the functions in libselinux
> >      such that the correct file contexts be applied at move time (i think!)
> 
> No kernel changes.
 
 [i mean by using libselinux1 in standard way]

> >  well, under most circumstances, i believe that can be catered for
> >  (with /etc/init.d/xfs creating /tmp/.font-unix being a notable
> >   exception).
> 
> test -s /sbin/restorecon && /sbin/restorecon /tmp/.font-unix

 (in /etc/init.d/xfs i've used if [ -x /sbin/restorecon ]; then /sbin....
  but hey it's all the same)

  l.


--
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:[~2004-09-07 12:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 23:41 dpkg and selinux Luke Kenneth Casson Leighton
2004-09-01  2:12 ` Scott James Remnant
2004-09-01 10:19   ` Luke Kenneth Casson Leighton
2004-09-01 13:30     ` Scott James Remnant
2004-09-01 17:25       ` Luke Kenneth Casson Leighton
2004-09-01 20:50         ` Scott James Remnant
2004-09-01 21:32           ` Luke Kenneth Casson Leighton
2004-09-01 22:29             ` Scott James Remnant
2004-09-07 12:20         ` Russell Coker
2004-09-07 12:39           ` Luke Kenneth Casson Leighton [this message]
2004-09-08 13:32             ` Russell Coker
2004-09-08 22:02               ` Luke Kenneth Casson Leighton
2004-09-07 12:25       ` Russell Coker
2004-09-01 17:47     ` Luke Kenneth Casson Leighton
2004-09-07 12:13       ` Russell Coker

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=20040907123930.GD17760@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-dpkg@lists.debian.org \
    --cc=russell@coker.com.au \
    --cc=scott@netsplit.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.