All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Want to make typeattribute declarations possible in conditionals
Date: Tue, 23 Jul 2013 14:22:07 +0200	[thread overview]
Message-ID: <20130723122207.GA21664@siphos.be> (raw)

Hi all,

I would like to be able to assign attributes to types in a conditional
statement. Right now, this isn't allowed, and I don't know if it is feasible
to look for a solution to this or not. Is this a real design constraint that
will be hard to work around, or is this doable?

Alternatives that I see are:
- making the assignations part of separate, small SELinux modules that users can unload/load
- using interfaces that assign the permissions to the given domain, and use
  this interface against the attribute. This will probably result in two
  interfaces, foo_domain() to assign the attribute (for non-tunable usage)
  and foo_domain_privileges() to assign the rights (for tunable usage) -
  naming convention notwithstanding here.
- decouple the requirement from the policy and let administrators do this

The last approach means that the policy doesn't include the definitions
anymore, instead providing a method (in the SELinux userspace utilities or
distribution-specific) to assign attributes.

For instance (mock-up):

~# semanage attribute -a -t mailserver_domain portage_t

This would then create (or maintain) a small module that does the necessary
declarations, like "typeattribute portage_t mailserver_domain".

What is your opinion on this? Weird request?

Wkr,
	Sven Vermeulen

             reply	other threads:[~2013-07-23 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 12:22 Sven Vermeulen [this message]
2013-07-23 13:13 ` [refpolicy] Want to make typeattribute declarations possible in conditionals Daniel J Walsh
2013-07-23 13:54 ` Christopher J. PeBenito
2013-07-23 13:54   ` Christopher J. PeBenito
2013-07-23 19:50   ` Sven Vermeulen
2013-07-23 19:50     ` Sven Vermeulen
2013-07-23 20:08     ` Joshua Brindle

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=20130723122207.GA21664@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.com \
    /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.