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