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: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: policy for k3b (and cdrecord)
Date: Wed, 18 Aug 2004 16:37:31 +0100	[thread overview]
Message-ID: <20040818153731.GF19646@lkcl.net> (raw)
In-Reply-To: <200408182054.46451.russell@coker.com.au>

On Wed, Aug 18, 2004 at 08:54:46PM +1000, Russell Coker wrote:
> On Wed, 18 Aug 2004 04:33, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > i'm writing a policy for k3b (kde cd burner) and cdrecord because
> > write access by users to /dev/hdc is banned (policy violation) and
> > because, well, because.
> 
> Why not change the type of /dev/hdc to removable_device_t and define 
> user_rw_noexattrfile when compiling the policy?  That should be all that the 
> CD burner needs.

 drat.  thank you.

 now why didn't i think of changing the type of /dev/hdc?

 hey, well, i've done the policy now, i might as well use it.

 unless.... of course... DVD and CD _reading_ *sigh*.

 that's up the creek, too.

 which your suggestion would fix as well.

 thank you russell: advice really appreciated, you saved me a lot of
 time and hassle.



> If you have a special policy for burning CDs then that policy needs to be 
> limited to only files that the user can access.
> 
> > - for more generic use, obviously k3b must be allowed to access pretty
> >   much anything on / so what should i put in place of all the
> >   dontaudits and allow k3b_t user_home_t etc. stuff?
> 
> If you have a domain k3b_t which is entered from any user domain then user_t 
> can use it to write files from a staff_r home directory to a CD...
 
 i allowed a lot of getattrs for directory access (and then removed
 them / turned them into dontaudits) before i realised of course that
 k3b was directory-scanning with find.

 once i realised that, i began to be more selective: i don't believe i
 added permission to read or scan the contents of /root for example.

 so really i should do something similar to the mozilla thing, then.

 namely, macro-ise it, use x_client_domain, that sort of thing.

 
 [btw it turns out that k3b doesn't actually do any cd-burning itself:
  it's just a front-end to running cdrecord, cdrdao and dvd+rw-format.]

 l.

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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-08-18 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 18:33 policy for k3b (and cdrecord) Luke Kenneth Casson Leighton
2004-08-18 10:54 ` Russell Coker
2004-08-18 15:37   ` Luke Kenneth Casson Leighton [this message]

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=20040818153731.GF19646@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=russell@coker.com.au \
    --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.