From: "Kim Hyung Chan" <kimhc@kjist.ac.kr>
To: <selinux@tycho.nsa.gov>
Subject: Transitivity in role dominance relation
Date: Thu, 13 Feb 2003 07:49:20 +0900 [thread overview]
Message-ID: <001201c2d2e8$fb235e80$7233edcb@kari> (raw)
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
With the well-documented manuals, I'm successfully testing
several access control policies. (Thanks to all contributors :) )
I've been testing role dominance relation. expecially,
the transitivity of role dominance relation.
prof_r > (osg_r, dbg_r) > stud_r
as;
dominance { role prof_r { role osg_r; role dbg_r; } }
dominance { role osg_r { role stud_r; } }
dominance { role dbg_r { role stud_r; } }
# disabled direct relation
#dominance { role prof_r { role stud_r; } }
In the above relation, I guessed that the prof_r role can not inherit
the types of stud_r as seeing below;
login: dilee_u
Password:
Your default context is dilee_u:osg_r:osg_t.
Do you want to choose a different one? [n]y
[1] dilee_u:osg_r:osg_t
[2] dilee_u:dbg_r:dbg_t
[3] dilee_u:prof_r:prof_t
Enter number of choice:
And I also could not get the context of stud_r using the newrole command
after getting the context of osg_r or dbg_r.
Any comments on this problem???
Have a nice day.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Hyung Chan Kim
Security Group, Concurrent System Research Laboratory
Dept. of Information and Communications
Kwangju Institute of Science and Technology (K-JIST)
1 Oryong-dong Buk-ku Gwangju 500-712, Rep. of Korea
Lab. : +82-62-970-2266
Fax : +82-62-970-2204
Mobile : +82-11-9660-4900
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 3037 bytes --]
next reply other threads:[~2003-02-12 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 22:49 Kim Hyung Chan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 16:09 Transitivity in role dominance relation 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='001201c2d2e8$fb235e80$7233edcb@kari' \
--to=kimhc@kjist.ac.kr \
--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.