All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: CIL: question with regard to CIL ioctl filtering support and neverallow
Date: Fri, 13 Nov 2015 16:28:31 +0100	[thread overview]
Message-ID: <20151113152830.GA21890@x250> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


This commit added iotctl whitelisting support to CIL:
https://github.com/SELinuxProject/selinux/commit/ef93dfe0393c4a60483c3f7729dd98a2f886606a

then later CIL whitelisting was extended with neverallow support here:
https://github.com/SELinuxProject/selinux/commit/99fc177b5af4e1e8855d42d2d01cb93ac7f9d14b

would the CIL ioctl whitelisting support have to be extended with the
ioctl whitelisting neverallow support as well?


- -- 
02DFF788
4D30 903A 1CF3 B756 FB48  1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQGcBAEBCgAGBQJWRgGZAAoJENAR6kfG5xmcZQQL/1ZzGHtKxJRYeyXn9rdrihG3
p5RgNiqNYrdlTHv2OF6E8YrTQ9pr6Qcg06x3aIMyewT3X/MekVN8B4Ren09oEqdR
50Oxw10/qPGSGglyU8o/jg+/gTUXHBUS3WYMIRtnTO0FkeZ+qEarF9FA/eNK1md+
AQ+ZLBVzXrU3Y386+AoBmi9MbE2YpVZ2D1O+3W4yssK15vsZatt3fTxs43K05rdX
9LrSPk2yl9RoICqWfPyvDPvgI3XCDynHktxs2mwuHkitnpAzWnKGPt1okaLVkrEu
lgLcum4aPHAGy+hBNCi+p7lVSa9+J4kCYCQ89Q1jno9Dj6mDt+SqECFMB/peeAN0
GCdotRhsf/lf1pi3fl0oS2UhUMOe6585ac0v/iPX+pEdJ7Tn/Kqqz4j78FSmpqbu
tO0RJa7v6+Ud5f5YiL84+ikzMe7DeVoeP1MM/laPBjB+Jg8/Lp9Bid9Iuk2yZjOd
xQBsvYuYowA8SfjNYafGAqfr477poW4L6lEPGdVVTg==
=JKo/
-----END PGP SIGNATURE-----

             reply	other threads:[~2015-11-13 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 15:28 Dominick Grift [this message]
2015-11-13 15:40 ` CIL: question with regard to CIL ioctl filtering support and neverallow Steve Lawrence

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=20151113152830.GA21890@x250 \
    --to=dac.override@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.