1.\"- 2.\" Copyright (c) 2000 Robert N. M. Watson 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 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. 13.\" 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 24.\" SUCH DAMAGE. 25.\" 26.\" $FreeBSD$ 27.\" 28.Dd January 17, 2000 29.Dt POSIX1E 3 30.Os FreeBSD 4.0 31.Sh NAME 32.Nm posix1e 33.Nd introduction to the POSIX.1e security API 34.Sh SYNOPSIS 35.Fd #include <sys/acl.h> 36.Fd #include <sys/audit.h> 37.Fd #include <sys/capability.h> 38.Fd #include <sys/mac.h> 39.Sh DESCRIPTION 40The IEEE POSIX.1e specification never left draft form, but the interfaces 41it describes are now widely used despite inherent limitations. Currently, 42only a few of the interfaces and features are implemented in FreeBSD, 43although efforts are underway to complete the integration at this time. 44 45POSIX.1e describes five security extensions to the base POSIX.1 API: 46Access Control Lists (ACLs), Auditing, Capabilities, Mandatory Access 47Control, and Information Flow Labels. Of these, the ACL interfaces are 48currently included with FreeBSD, Auditing, Capabilities, and Mandatory 49Access Control are in the wings, and Information Flow Labels are not on 50the calendar. 51 52POSIX.1e defines both syntax and semantics for these features, but fairly 53substantial changes are required to implement these features in the 54operating system. As shipped, FreeBSD 4.0 permits file systems to export 55Access Control Lists via the VFS, and provides a library for userland 56access to and manipulation of these ACLs, but support for ACLs is not 57provided by any file systems shipped in the base operating system. 58Available API calls relating to ACLs are described in detail in 59.Xr acl 3 . 60 61The patches supporting other POSIX.1e features are not available in the 62base operating system at this time--however, more information on them 63may be found on the FreeBSD POSIX.1e implementation web page: 64 65http://www.watson.org/fbsd-hardening/posix1e/ 66.Sh IMPLEMENTATION NOTES 67FreeBSD's support for POSIX.1e interfaces and features is still under 68development at this time. 69.Sh ENVIRONMENT 70POSIX.1e assigns security labels to all objects, extending the security 71functionality described in POSIX.1. These additional labels provide 72fine-grained discretionary access control, fine-grained capabilities, 73and labels necessary for mandatory access control. POSIX.2c describes 74a set of userland utilities for manipulating these labels. These userland 75utilities are not bundled with 76.Fx 4.0 77so as to discourage their 78use in the short term. 79.Sh FILES 80.Sh SEE ALSO 81.Xr acl 3 , 82.Xr acl 9 , 83.Xr extattr 9 84.Sh STANDARDS 85POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion 86of the draft continues on the cross-platform POSIX.1e implementation 87mailing list. To join this list, see the 88.Fx 89POSIX.1e implementation 90page for more information. 91.Sh HISTORY 92POSIX.1e support was introduced in 93.Fx 4.0 , 94and development continues. 95.Sh AUTHORS 96.An Robert N M Watson , 97.An Ilmar S Habibulin 98.Sh BUGS 99These features are not yet fully implemented. In particular, the shipped 100version of UFS/FFS does not support storage of additional security labels, 101and so is unable to (easily) provide support for most of these features. 102