diff options
| author | bdrewery <bdrewery@FreeBSD.org> | 2016-06-27 20:31:56 +0000 |
|---|---|---|
| committer | bdrewery <bdrewery@FreeBSD.org> | 2016-06-27 20:31:56 +0000 |
| commit | 72a174f20a2a60cf397c37a636a3e3230b6a114c (patch) | |
| tree | f86875d968949cdb45fa17863fb1eff0662ba7ea | |
| parent | 4542c2afc3d1697def1e77a37b7d0a773ee40964 (diff) | |
| download | FreeBSD-src-72a174f20a2a60cf397c37a636a3e3230b6a114c.zip FreeBSD-src-72a174f20a2a60cf397c37a636a3e3230b6a114c.tar.gz | |
MFC r296285:
Correct a comment.
| -rw-r--r-- | sys/kern/kern_exec.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/kern/kern_exec.c b/sys/kern/kern_exec.c index 47ea9b0..188eba7 100644 --- a/sys/kern/kern_exec.c +++ b/sys/kern/kern_exec.c @@ -671,7 +671,7 @@ interpret: * Don't honor setuid/setgid if the filesystem prohibits it or if * the process is being traced. * - * We disable setuid/setgid/etc in compatibility mode on the basis + * We disable setuid/setgid/etc in capability mode on the basis * that most setugid applications are not written with that * environment in mind, and will therefore almost certainly operate * incorrectly. In principle there's no reason that setugid |
