acl_valid.3 (32eef9aeb1f39a1623cea55da147c89abbd5b9a5) acl_valid.3 (6394f703dcdf80f1fd010d508645732880f46d93)
1.\"-
1.\"-
2.\" Copyright (c) 2000 Robert N. M. Watson
2.\" Copyright (c) 2000, 2002 Robert N. M. Watson
3.\" All rights reserved.
4.\"
3.\" All rights reserved.
4.\"
5.\" This software was developed by Robert Watson for the TrustedBSD Project.
6.\"
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.

--- 7 unchanged lines hidden (view full) ---

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.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\" notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\" notice, this list of conditions and the following disclaimer in the
14.\" documentation and/or other materials provided with the distribution.

--- 7 unchanged lines hidden (view full) ---

22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\" $FreeBSD$
29.\"
28.Dd January 28, 2000
30.Dd December 29, 2002
29.Dt ACL_VALID 3
30.Os
31.Sh NAME
32.Nm acl_valid ,
33.Nm acl_valid_fd_np ,
31.Dt ACL_VALID 3
32.Os
33.Sh NAME
34.Nm acl_valid ,
35.Nm acl_valid_fd_np ,
34.Nm acl_valid_file_np
36.Nm acl_valid_file_np ,
37.Nm acl_valid_link_np
35.Nd validate an ACL
36.Sh LIBRARY
37.Lb libc
38.Sh SYNOPSIS
39.In sys/types.h
40.In sys/acl.h
41.Ft int
42.Fn acl_valid "acl_t acl"
43.Ft int
44.Fn acl_valid_fd_np "int fd" "acl_type_t type" "acl_t acl"
45.Ft int
46.Fn acl_valid_file_np "const char *path_p" "acl_type_t type" "acl_t acl"
38.Nd validate an ACL
39.Sh LIBRARY
40.Lb libc
41.Sh SYNOPSIS
42.In sys/types.h
43.In sys/acl.h
44.Ft int
45.Fn acl_valid "acl_t acl"
46.Ft int
47.Fn acl_valid_fd_np "int fd" "acl_type_t type" "acl_t acl"
48.Ft int
49.Fn acl_valid_file_np "const char *path_p" "acl_type_t type" "acl_t acl"
50.Ft int
51.Fn acl_valid_link_np "const char *path_p" "acl_type_t type" "acl_t acl"
47.Sh DESCRIPTION
48These functions check that the ACL referred to by the argument
49.Va acl
50is valid. The POSIX.1e routine,
51.Fn acl_valid ,
52checks this validity only with POSIX.1e ACL semantics, and irrespective
53of the context in which the ACL is to be used. The non-portable forms,
52.Sh DESCRIPTION
53These functions check that the ACL referred to by the argument
54.Va acl
55is valid. The POSIX.1e routine,
56.Fn acl_valid ,
57checks this validity only with POSIX.1e ACL semantics, and irrespective
58of the context in which the ACL is to be used. The non-portable forms,
54.Fn acl_valid_fd_np
55and
59.Fn acl_valid_fd_np ,
56.Fn acl_valid_file_np ,
60.Fn acl_valid_file_np ,
61and
62.Fn acl_valid_link_np
57allow an ACL to be checked in the context of a specific acl type,
58.Va type ,
63allow an ACL to be checked in the context of a specific acl type,
64.Va type ,
59and file system object. In environments where additional ACL types are
65and file system object.
66In environments where additional ACL types are
60supported than just POSIX.1e, this makes more sense.
67supported than just POSIX.1e, this makes more sense.
68Whereas
69.Fn acl_valid_file_np
70will follow the symlink if the specified path is to a symlink,
71.Fn acl_valid_link_np
72will not.
61.Pp
62For POSIX.1e semantics, the checks include:
63.Bd -literal -offset indent
64The three required entries (ACL_USER_OBJ, ACL_GROUP_OBJ,
65and ACL_OTHER) shall exist exactly once in the ACL. If
66the ACL contains any ACL_USER, ACL_GROUP, or any other
67implementation-defined entries in the file group class
68then one ACL_MASK entry shall also be required. The ACL

--- 66 unchanged lines hidden (view full) ---

135POSIX.1e implementation
136page for more information.
137.Sh HISTORY
138POSIX.1e support was introduced in
139.Fx 4.0 ,
140and development continues.
141.Sh AUTHORS
142.An Robert N M Watson
73.Pp
74For POSIX.1e semantics, the checks include:
75.Bd -literal -offset indent
76The three required entries (ACL_USER_OBJ, ACL_GROUP_OBJ,
77and ACL_OTHER) shall exist exactly once in the ACL. If
78the ACL contains any ACL_USER, ACL_GROUP, or any other
79implementation-defined entries in the file group class
80then one ACL_MASK entry shall also be required. The ACL

--- 66 unchanged lines hidden (view full) ---

147POSIX.1e implementation
148page for more information.
149.Sh HISTORY
150POSIX.1e support was introduced in
151.Fx 4.0 ,
152and development continues.
153.Sh AUTHORS
154.An Robert N M Watson
143.Sh BUGS
144These features are not yet fully implemented.