Current version
Git/Latestdiff: 1.5.6
Latest Snapshots
Produced after each commit or rebase to new upstream version
GIT
RSBAC source code, can be unstable sometimes
No events planned
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
documentation:rsbac_handbook:appendixes:rsbac_reference:targets_and_requests [2009/01/13 13:33] 127.0.0.1 (old revision restored) |
documentation:rsbac_handbook:appendixes:rsbac_reference:targets_and_requests [2009/01/13 13:35] 127.0.0.1 (old revision restored) |
||
---|---|---|---|
Line 2: | Line 2: | ||
RSBAC restricts access by subjects to objects. The subjects are always | RSBAC restricts access by subjects to objects. The subjects are always | ||
processes, acting on the behalf of a user with certain attributes, like system_role etc. | processes, acting on the behalf of a user with certain attributes, like system_role etc. | ||
+ | |||
==== Targets ==== | ==== Targets ==== | ||
Line 13: | Line 14: | ||
| DEV |Devices, identified by type (char or block), major and minor number| | | DEV |Devices, identified by type (char or block), major and minor number| | ||
| IPC |InterProcess Communication: Semaphores (sem), Messages (msg), Shared Memory (shm), Sockets (sock)| | | IPC |InterProcess Communication: Semaphores (sem), Messages (msg), Shared Memory (shm), Sockets (sock)| | ||
+ | | UNIXSOCK |Unix sockets| | ||
| SCD |System Control Data: Objects affecting the whole system. This target type is the only one with a fixed number of objects, identified by number (see below).| | | SCD |System Control Data: Objects affecting the whole system. This target type is the only one with a fixed number of objects, identified by number (see below).| | ||
| USER |Users as objects, mostly for access control information (ACI).| | | USER |Users as objects, mostly for access control information (ACI).| |