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

On Wed, 1 Sep 2004 23:30, Scott James Remnant <scott@netsplit.com> wrote:
> It's an interesting one, certainly I'd suggest the right solution would
> be to do such commands in postinst until such time as it was the default
> and the tar format could carry this information.  It would then become
> policy that it would be carried inside the tar file, just as chmod/
> chgrp/chown are carried today.

The problem with that idea is that there are many possible policies.  Fedora 
currently has two significantly different policies which require different 
file labels on disk.  Storing the data in the package for such things is not 
going to work (and would require that all DDs have some SE Linux files 
installed on their systems).

The right solution is to apply the regex set at install time.

> The thing that worries me about this file is that it contains policy for
> things I don't have installed on my system; and doesn't seem to cope
> well with differing policy for (e.g.) two binaries called 'ssh' which
> may have different requirements.

Only one binary can have the full path /usr/bin/ssh which is what matters.

> However I'm loath to embed specific selinux support into dpkg if it
> introduces extra dependencies, or causes problems for those not using
> it.

Getting it to work in Debian should not be difficult.  Having a shared object 
interface to make the SE Linux library a plug-in and thus support RSBAC etc 
also shouldn't be too difficult.

> > i think only stephen, russell, dan or colin are in a position to
> > answer that.
>
> Sadly they've stopped answering my calls <g>

No, I've just been busy recently.  I've got about 1600 messages to catch up on 
at the moment...

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
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.

  parent reply	other threads:[~2004-09-07 12:25 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
2004-09-08 13:32             ` Russell Coker
2004-09-08 22:02               ` Luke Kenneth Casson Leighton
2004-09-07 12:25       ` Russell Coker [this message]
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=200409072225.41258.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-dpkg@lists.debian.org \
    --cc=lkcl@lkcl.net \
    --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.