From: Debian User <rogelio@evoworks.evoserve.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: automatic type transitions for pts in devfs
Date: Tue, 09 Jul 2002 22:19:49 +0800 [thread overview]
Message-ID: <3D2AF105.8080008@evoworks.evoserve.com> (raw)
In-Reply-To: Pine.GSO.4.33.0207091011390.27193-100000@raven
Stephen Smalley wrote:
>On Tue, 9 Jul 2002, Debian User wrote:
>
>
>
>>So I focus on hooks.c. This is basically getting the inodes labelled
>>correctly.
>>Either we add some new fields(?) in the inode structure or we insert a
>>condition that would make the inode get the proper label. Is that correct?
>>
>>
>
>You could add a test within the sbsec->uses_genfs case to see whether the
>filesystem type is devfs and whether the inode corresponds to a /pts node.
>If so, then you want to use a transition SID as with the sbsec->uses_trans
>case. Otherwise, you would use genfs_contexts as usual.
>
>
cool! i see it now. this is great. this is the first time i hacked devfs
and selinux!
Thanks!
>--
>Stephen D. Smalley, NAI Labs
>ssmalley@nai.com
>
>
>
>
--
You have received this message because you are subscribed to the selinux 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:[~2002-07-09 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 12:49 automatic type transitions for pts in devfs Debian User
2002-07-09 13:26 ` Stephen Smalley
2002-07-09 13:41 ` Debian User
2002-07-09 14:07 ` Stephen Smalley
2002-07-09 14:17 ` Debian User
2002-07-09 14:02 ` Debian User
2002-07-09 14:16 ` Stephen Smalley
2002-07-09 14:19 ` Debian User [this message]
2002-07-09 14:33 ` Debian User
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 3:26 Debian User
2002-07-11 12:20 ` Stephen Smalley
2002-07-11 12:35 ` Debian User
2002-07-11 13:03 ` Stephen Smalley
2002-03-06 12:45 Russell Coker
2002-03-06 13:41 ` Stephen Smalley
2002-03-09 13:04 ` Russell Coker
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=3D2AF105.8080008@evoworks.evoserve.com \
--to=rogelio@evoworks.evoserve.com \
--cc=sds@tislabs.com \
--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.