xref: /dragonfly/lib/libc/sys/chmod.2 (revision 8edfbc5e)
1.\" Copyright (c) 1980, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
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.\"     @(#)chmod.2	8.1 (Berkeley) 6/4/93
29.\" $FreeBSD: src/lib/libc/sys/chmod.2,v 1.16.2.7 2001/12/14 18:34:00 ru Exp $
30.\"
31.Dd August 3, 2016
32.Dt CHMOD 2
33.Os
34.Sh NAME
35.Nm chmod ,
36.Nm fchmod ,
37.Nm lchmod ,
38.Nm fchmodat
39.Nd change mode of file
40.Sh LIBRARY
41.Lb libc
42.Sh SYNOPSIS
43.In sys/stat.h
44.Ft int
45.Fn chmod "const char *path" "mode_t mode"
46.Ft int
47.Fn fchmod "int fd" "mode_t mode"
48.Ft int
49.Fn lchmod "const char *path" "mode_t mode"
50.Ft int
51.Fn fchmodat "int dirfd" "const char *path" "mode_t mode" "int flags"
52.Sh DESCRIPTION
53The file permission bits of the file named specified by
54.Fa path
55or referenced by the file descriptor
56.Fa fd
57are changed to
58.Fa mode .
59The
60.Fn chmod
61function verifies that the process owner (user) either owns
62the file specified by
63.Fa path
64(or
65.Fa fd ) ,
66or
67is the super-user.
68The
69.Fn chmod
70function follows symbolic links to operate on the target of the link
71rather than the link itself.
72.Pp
73The
74.Fa lchmod
75function is similar to
76.Fn chmod
77but does not follow symbolic links.
78.Pp
79The
80.Fn fchmodat
81function is equivalent to the
82.Fn chmod
83or
84.Fn lchmod
85functions except in the case where the
86.Fa path
87specifies a relative path.
88In this case the file to be opened is determined relative to the directory
89associated with the file descriptor
90.Fa dirfd
91instead of the current working directory.
92If
93.Fn fchmodat
94is passed the special value
95.Dv AT_FDCWD
96in the
97.Fa dirfd
98parameter, the current working directory is used
99and the behavior is identical to a call to
100.Fn chmod
101or
102.Fn lchmod .
103.Pp
104A mode is created from
105.Em or'd
106permission bit masks
107defined in
108.In sys/stat.h :
109.Pp
110.Bd -literal -offset indent -compact
111#define S_IRWXU 0000700    /* RWX mask for owner */
112#define S_IRUSR 0000400    /* R for owner */
113#define S_IWUSR 0000200    /* W for owner */
114#define S_IXUSR 0000100    /* X for owner */
115
116#define S_IRWXG 0000070    /* RWX mask for group */
117#define S_IRGRP 0000040    /* R for group */
118#define S_IWGRP 0000020    /* W for group */
119#define S_IXGRP 0000010    /* X for group */
120
121#define S_IRWXO 0000007    /* RWX mask for other */
122#define S_IROTH 0000004    /* R for other */
123#define S_IWOTH 0000002    /* W for other */
124#define S_IXOTH 0000001    /* X for other */
125
126#define S_ISUID 0004000    /* set user id on execution */
127#define S_ISGID 0002000    /* set group id on execution */
128#define S_ISVTX 0001000    /* sticky bit */
129#if __BSD_VISIBLE
130#define S_ISTXT 0001000
131#endif
132.Ed
133.Pp
134The
135.Dx
136VM system totally ignores the sticky bit
137.Pq Dv ISVTX
138for executables.
139On UFS-based filesystems (FFS, MFS, LFS) the sticky
140bit may only be set upon directories.
141.Pp
142If mode
143.Dv ISVTX
144(the `sticky bit') is set on a directory,
145an unprivileged user may not delete or rename
146files of other users in that directory.
147The sticky bit may be
148set by any user on a directory which the user owns or has appropriate
149permissions.
150For more details of the properties of the sticky bit, see
151.Xr sticky 8 .
152.Pp
153If mode ISUID (set UID) is set on a directory, and the
154.Dv MNT_SUIDDIR
155option was used in the mount of the filesystem,
156then the owner of any new files and sub-directories
157created within this directory are set
158to be the same as the owner of that directory.
159If this function is enabled, new directories will inherit
160the bit from their parents.
161Execute bits are removed from the file, and it will not be given to root.
162This behavior does not change the
163requirements for the user to be allowed to write the file, but only the eventual
164owner after it has been created.
165Group inheritance is not affected.
166.Pp
167This feature is designed for use on fileservers serving PC users via
168ftp or SAMBA.
169It provides security holes for shell users and as
170such should not be used on shell machines, especially on home directories.
171This option requires the SUIDDIR
172option in the kernel to work.
173Only UFS filesystems support this option.
174For more details of the suiddir mount option, see
175.Xr mount 8 .
176.Pp
177Writing or changing the owner of a file
178turns off the set-user-id and set-group-id bits
179unless the user is the super-user.
180This makes the system somewhat more secure
181by protecting set-user-id (set-group-id) files
182from remaining set-user-id (set-group-id) if they are modified,
183at the expense of a degree of compatibility.
184.Pp
185The values for the
186.Fa flags
187are constructed by a bitwise-inclusive OR of flags from the following list,
188defined in
189.In fcntl.h :
190.Bl -tag -width indent
191.It Dv AT_SYMLINK_NOFOLLOW
192If
193.Fa path
194names a symbolic link, the mode of the symbolic link is changed.
195.El
196.Sh RETURN VALUES
197.Rv -std
198.Sh ERRORS
199.Fn Chmod ,
200.Fn lchmod
201and
202.Fn fchmodat
203will fail and the file mode will be unchanged if:
204.Bl -tag -width Er
205.It Bq Er ENOTDIR
206A component of the path prefix or
207.Fa dirfd
208is not a directory.
209.It Bq Er ENAMETOOLONG
210A component of a pathname exceeded 255 characters,
211or an entire path name exceeded 1023 characters.
212.It Bq Er ENOENT
213The named file does not exist.
214.It Bq Er EACCES
215Search permission is denied for a component of the path prefix.
216.It Bq Er ELOOP
217Too many symbolic links were encountered in translating the pathname.
218.It Bq Er EPERM
219The effective user ID does not match the owner of the file and
220the effective user ID is not the super-user.
221.It Bq Er EROFS
222The named file resides on a read-only file system.
223.It Bq Er EFAULT
224.Fa Path
225points outside the process's allocated address space.
226.It Bq Er EIO
227An I/O error occurred while reading from or writing to the file system.
228.It Bq Er EFTYPE
229An attempt was made to set the sticky bit upon an executable.
230.El
231.Pp
232.Fn Fchmod
233will fail if:
234.Bl -tag -width Er
235.It Bq Er EBADF
236The descriptor is not valid.
237.It Bq Er EINVAL
238.Fa fd
239refers to a socket, not to a file.
240.It Bq Er EROFS
241The file resides on a read-only file system.
242.It Bq Er EIO
243An I/O error occurred while reading from or writing to the file system.
244.El
245.Sh SEE ALSO
246.Xr chmod 1 ,
247.Xr chown 2 ,
248.Xr open 2 ,
249.Xr stat 2 ,
250.Xr sticky 8
251.Sh STANDARDS
252The
253.Fn chmod
254function call is expected to conform to
255.St -p1003.1-90 ,
256except for the return of
257.Er EFTYPE
258and the use of
259.Dv S_ISTXT .
260.Sh HISTORY
261A
262.Fn chmod
263function call appeared in
264.At v7 .
265The
266.Fn fchmod
267function call
268appeared in
269.Bx 4.2 .
270The
271.Fn lchmod
272function call appeared in
273.Fx 3.0 .
274.Pp
275The
276.Fn fchmodat
277system call appeared in
278.Dx 2.3 .
279