2 .\" Copyright (c) 2000 Robert N. M. Watson
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd introduction to the POSIX.1e security API
40 .\" .In sys/capability.h
43 The IEEE POSIX.1e specification never left draft form, but the interfaces
44 it describes are now widely used despite inherent limitations.
45 Currently, only a few of the interfaces and features are implemented in
47 although efforts are underway to complete the integration at this time.
49 POSIX.1e describes five security extensions to the base POSIX.1 API:
50 Access Control Lists (ACLs), Auditing, Capabilities, Mandatory Access
51 Control, and Information Flow Labels.
53 supports POSIX.1e ACL interfaces, as well as POSIX.1e-like MAC
55 The TrustedBSD Project has produced but not integrated an implementation
56 of POSIX.1e Capabilities.
58 POSIX.1e defines both syntax and semantics for these features, but fairly
59 substantial changes are required to implement these features in the
64 provides API and VFS support for ACLs, but not an implementation on any
67 includes support for ACLs as part of UFS1 and UFS2, as well as necessary
68 VFS support for additional file systems to export ACLs as appropriate.
69 Available API calls relating to ACLs are described in detail in
74 includes support for Mandatory Access Control as well as POSIX.1e-like
75 APIs for label management.
76 More information on API calls relating to MAC is available in
79 Additional patches supporting POSIX.1e features are provided by the
82 http://www.TrustedBSD.org/
83 .Sh IMPLEMENTATION NOTES
85 support for POSIX.1e interfaces and features is still under
86 development at this time, and many of these features are considered new
89 POSIX.1e assigns security labels to all objects, extending the security
90 functionality described in POSIX.1.
91 These additional labels provide
92 fine-grained discretionary access control, fine-grained capabilities,
93 and labels necessary for mandatory access control.
95 a set of userland utilities for manipulating these labels.
97 Many of these services are supported by extended attributes, documented
102 While these APIs are not documented in POSIX.1e, they are similar in
112 POSIX.1e is described in IEEE POSIX.1e draft 17.
113 Discussion of the draft continues
114 on the cross-platform POSIX.1e implementation
116 To join this list, see the
118 POSIX.1e implementation
119 page for more information.
121 POSIX.1e support was introduced in
123 most of the features are available as of
125 Development continues.
127 .An Robert N M Watson
128 .An Chris D. Faulhaber
130 .An Ilmar S Habibulin
132 Many of these features are considered new or experimental in
134 and should be deployed with appropriate caution.