From: Giorgio Zanin <selinux_list@yahoo.it>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Russell Coker <russell@coker.com.au>, selinux@tycho.nsa.gov
Subject: Re: about security contexts for objects
Date: Fri, 23 May 2003 10:09:11 +0200 [thread overview]
Message-ID: <3ECDD727.7030905@yahoo.it> (raw)
In-Reply-To: <1053631371.1032.43.camel@moss-huskers.epoch.ncsc.mil>
Stephen Smalley wrote:
>>Look at the policy for all types that have the attribute file_type, that
>>should catch all of them.
>>
Actually file_type, as it is just an attribute with no semantics with
respect to the configuration language, is not the thing I would look at.
I mean, attributes are just names associated with types with no
semantics from a language point of view. What I need is something with
semantics in the configuration language context.
I wouldn't use attributes values fot infering any property of a
configuration, becouse I can think at an attribute just as a collection
of types (attributes are useful but they are not necessary).
>>Not all of them. The file_type attribute is limited to files associated
>>with conventional (disk-based) filesystems and is used in allow rules
>>permitting the association of such types with those filesystems. It
>>doesn't cover types associated with pseudo filesystems.
>>
what are exactly all the kinds of pseudo files? Do they cover every
object class other than file-related ones (file, filesystem, dir,
fifo_file, ...) and process?
Giorgio
--
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.
next prev parent reply other threads:[~2003-05-23 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 14:10 about security contexts for objects Giorgio Zanin
2003-05-22 16:35 ` Russell Coker
2003-05-22 19:22 ` Stephen Smalley
2003-05-23 8:09 ` Giorgio Zanin [this message]
2003-05-23 11:26 ` Stephen 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=3ECDD727.7030905@yahoo.it \
--to=selinux_list@yahoo.it \
--cc=russell@coker.com.au \
--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.