aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2020-03-30 22:41:25 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2020-03-30 22:41:25 +0200
commit1f4cf8e85e88e62e977abb7326a70330fba9f861 (patch)
tree9a82816360498418a07b2dec8ced857a50647d3b
parent6b6505af4d4954c76947db4ecff889e83571338f (diff)
downloadman-pages-1f4cf8e85e88e62e977abb7326a70330fba9f861.tar.gz
openat2.2: srcfix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/openat2.22
1 files changed, 1 insertions, 1 deletions
diff --git a/man2/openat2.2 b/man2/openat2.2
index 20e1ffe101..9cbf389798 100644
--- a/man2/openat2.2
+++ b/man2/openat2.2
@@ -325,7 +325,7 @@ However, unlike
.B RESOLVE_IN_ROOT
allows a program to efficiently restrict path resolution on a per-open basis.
.\" FIXME The next piece is unclear (to me). What kind of ".." escape
-.\" attempts does chroot() not detecct that RESOLVE_IN_ROOT does?
+.\" attempts does chroot() not detect that RESOLVE_IN_ROOT does?
The
.B RESOLVE_IN_ROOT
flag also has several hardening features