From: dE <de.techno@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: Where's the class defined in file_contexts*
Date: Tue, 01 Jul 2014 23:27:20 +0530 [thread overview]
Message-ID: <53B2F680.7060603@gmail.com> (raw)
In-Reply-To: <53B2908B.3060407@redhat.com>
On 07/01/14 16:12, Daniel J Walsh wrote:
> On 07/01/2014 04:47 AM, dE wrote:
>> The default security context of a object also depends on it's class.
>>
>> I was looking at
>> etc/selinux/<SELINUXTYPE>/contexts/files/file_contexts*, but I
>> couldn't see any definition of a class.
>>
>> Also semanage fcontext doesn't have an option define a class. Entries
>> are based only on files and directories.
>>
>> If you get red text in this email please notify.
>> _______________________________________________
>> Selinux mailing list
>> Selinux@tycho.nsa.gov
>> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
>> To get help, send an email containing "help" to
>> Selinux-request@tycho.nsa.gov.
> I believe the answer to your question is:
>
> man semanage-fcontext
> ...
> -f [{a,f,d,c,b,s,l,p}], --ftype [{a,f,d,c,b,s,l,p}]
> File Type. This is used with fcontext. Requires a file
> type as shown in the mode field by ls, e.g. use 'd' to match only
> directories
> or 'f' to match only regular files. The following
> file type options can be passed: f (regular file),d (directory),c (character
> device), b (block device),s (socket),l (symbolic link),p
> (named pipe). If you do not specify a file type, the file type will
> default to "all files".
Thanks everyone for clarifying this.
I didnt know there existed man pages for semanage-*. It's not there in
Fedora 19.
next prev parent reply other threads:[~2014-07-01 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 8:47 Where's the class defined in file_contexts* dE
2014-07-01 10:36 ` Sven Vermeulen
2014-07-01 10:42 ` Daniel J Walsh
2014-07-01 17:57 ` dE [this message]
2014-07-01 10:45 ` Dominick Grift
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=53B2F680.7060603@gmail.com \
--to=de.techno@gmail.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.