From: Joshua Brindle <method@gentoo.org>
To: Mohammad Mahmoudi <mahmoudi1379@yahoo.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Revocation Support
Date: Sun, 28 May 2006 17:54:59 -0400 [thread overview]
Message-ID: <447A1C33.2040200@gentoo.org> (raw)
In-Reply-To: <20060528115017.96102.qmail@web50413.mail.yahoo.com>
Mohammad Mahmoudi wrote:
> Does SELinux support revocation of permissions?
>
The FLASK architecture, which SELinux is based on, does indeed support
revocation by allowing object managers to register callbacks with the
security server. However, on SELinux, this is not currently in use. So
direct revocation where the object managers actively remove access to
objects after a policy change doesn't happen.
However, on some object classes permission is revalidated on every
object use (like files and file descriptors). So, even though a process
has a file descriptor to a file it previously had access top open, if
the permissions change to that file type the next read or write
operation will fail which essentially revokes access to it. This should
be the case on a file types, fds, sockets, ipc (except shared memory).
Hope this helps..
<http://us.rd.yahoo.com/mymod/showtimes/X-Men:%20The%20Last%20Stand/SIG=13eg95e87/*https://www.movietickets.com/purchase.asp?afid=myyah&house_id=8612&movie_id=44681&perfd=05282006&perft=23:30>
--
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:[~2006-05-28 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 11:50 Revocation Support Mohammad Mahmoudi
2006-05-28 21:18 ` Erich Schubert
2006-05-28 21:54 ` Joshua Brindle [this message]
2006-05-28 22:14 ` Joshua Brindle
2006-05-30 15:12 ` Stephen Smalley
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=447A1C33.2040200@gentoo.org \
--to=method@gentoo.org \
--cc=SELinux@tycho.nsa.gov \
--cc=mahmoudi1379@yahoo.com \
/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.