All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giorgio Zanin <giorgio.zanin@inwind.it>
To: selinux@tycho.nsa.gov, sds@epoch.ncsc.mil
Subject: label transitions
Date: Fri, 29 Nov 2002 15:19:57 +0100	[thread overview]
Message-ID: <3DE7778D.9080703@inwind.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

I'm now investigating the mechanism used in SELinux to change 
something's security label.
I know there is a kernel interface and a system call for applications  
to do it, their name is security_transition_sid.

The configuration language has two constructs: type_transition and 
type_change. The first is used by the kernel and instructs the security 
server to return a particular label for a type pair and a class when the 
security_transition_sid is called to label a new object or a transformed 
process.

If type_transition is used to label a transformed process, it requires 
the transition permission of the class process.
What about type_transition for files? I mean I had a look at 
file_trans_macro and it seems it's not specified anything like the 
transition process permission to change the type of a file. How can I 
control the privilege to change the type of a new object?

Is it correct to argue that permissions relabelto, relabelfrom and 
transition of file class are used to grant applications the ability to 
change labels with a call to security_transition_sid (with the output 
label specified via type_change)?

Thanks in advance for your nth answer ;)

Giorgio

             reply	other threads:[~2002-11-29 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 14:19 Giorgio Zanin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29 21:42 label transitions Stephen D. Smalley

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=3DE7778D.9080703@inwind.it \
    --to=giorgio.zanin@inwind.it \
    --cc=sds@epoch.ncsc.mil \
    --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.