From: Dominick Grift <domg472@gmail.com>
To: selinux@tycho.nsa.gov
Cc: sbrandmair@gmx.net
Subject: Re: [SELinux] Wildcard for object classes?
Date: Sun, 06 Mar 2011 19:30:12 +0100 [thread overview]
Message-ID: <4D73D2B4.8070401@gmail.com> (raw)
In-Reply-To: <201103061032.21143.russell@coker.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/06/2011 12:32 AM, Russell Coker wrote:
> On Sat, 29 Jan 2011, Simon Brandmair <sbrandmair@gmx.net> wrote:
>> I just started looking into SELinux. I am wondering if there is a way to
>> have wildcards in avc rules like:
>> auditallow source_t target_t : * * ;
>> which audits all access from source_t to target_t.
>>
>> Or do I have to add all classes objects to the rule like:
>> auditallow source_t target_t : {appletalk_socket, association,
>> blk_file ... } * ;
>
> No, there isn't such a wildcard at this time (AFAIK). It might be worth
> adding one so I've moved this discussion to the SE Linux upstream mailing list
> (please don't CC debian-security on future replies).
>
Not possible and as far as i know neither is your second suggestion.
This is because not all permissions can be used with all object classes.
You would add a rule for each object class type (or set of object
classes that share the same permissions):
auditallow source target:notdevfile_class_set *;
auditallow source target:devfile_class_set *;
auditallow source target:socket_class_set *;
auditallow source target:file_class_set *;
etc, etc.
I am not sure if auditallow is the right way to do this. Maybe the audit
suite has better options for your requirements.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1z0rMACgkQMlxVo39jgT/t6gCg1T3AquC6RVeUpY2KEnQMdZT1
AowAoJgPYENYYXvTmRJVhtqSXpxKwFbv
=zUKb
-----END PGP SIGNATURE-----
--
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:[~2011-03-06 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ii11vf$vns$02$1@news.t-online.com>
2011-03-05 23:32 ` [SELinux] Wildcard for object classes? Russell Coker
2011-03-06 18:05 ` Guido Trentalancia
2011-03-06 18:30 ` Dominick Grift [this message]
2011-03-15 1:43 ` Dave Quigley
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=4D73D2B4.8070401@gmail.com \
--to=domg472@gmail.com \
--cc=sbrandmair@gmx.net \
--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.