From: Steve Grubb <sgrubb@redhat.com>
To: selinux@tycho.nsa.gov
Subject: Capabilities audit field
Date: Sun, 12 Oct 2008 09:07:07 -0400 [thread overview]
Message-ID: <200810120907.07511.sgrubb@redhat.com> (raw)
Hi,
I recenetly found out that the kernel now allows more than 32 capabilities.
This means I need to update the audit code that inteprets this value given
from SE Linux. When I looked over the 2.6.27 kernel code, I found that SE
Linux has not updated the capabilities code. Its still being kept as a simple
integer in avc.h, but everywhere else I look in the kernel has moved to
kernel_cap_t, which is an array. Are patches for moving to kernel_cap_t
scheduled for 2.6.28? Are there security implications for not being able to
access or control capabilities > 32?
Thanks,
-Steve
--
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 reply other threads:[~2008-10-12 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 13:07 Steve Grubb [this message]
2008-10-12 23:12 ` Capabilities audit field James Morris
2008-10-13 10:35 ` Steve Grubb
2008-10-13 22:54 ` James Morris
2008-10-13 23:27 ` Steve Grubb
2008-10-14 9:21 ` James Morris
2008-10-14 13:35 ` Stephen Smalley
2008-10-12 23:18 ` Joshua Brindle
2008-10-13 4:05 ` James Morris
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=200810120907.07511.sgrubb@redhat.com \
--to=sgrubb@redhat.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.