|
 |
0e1944 |
diff -up ./doc/sudoers.cat.lookup ./doc/sudoers.cat
|
|
|
0e1944 |
--- ./doc/sudoers.cat.lookup 2017-04-25 13:17:51.073190114 +0200
|
|
|
0e1944 |
+++ ./doc/sudoers.cat 2017-04-25 13:17:51.081190069 +0200
|
|
|
0e1944 |
@@ -1140,24 +1140,39 @@ S?SU?UD?DO?OE?ER?RS?S O?OP?PT?TI?IO?ON?N
|
|
|
0e1944 |
_?o_?n by default.
|
|
|
0e1944 |
|
|
|
0e1944 |
match_group_by_gid
|
|
|
0e1944 |
- By default, when matching groups, s?su?ud?do?oe?er?rs?s will first
|
|
|
0e1944 |
- resolve all the user's group IDs to group names and
|
|
|
0e1944 |
- then compare those group names to any group names
|
|
|
0e1944 |
- listed in the _?s_?u_?d_?o_?e_?r_?s file. This works well on systems
|
|
|
0e1944 |
- where the number of groups listed in the _?s_?u_?d_?o_?e_?r_?s file
|
|
|
0e1944 |
- is larger than the number of groups a typical user
|
|
|
0e1944 |
- belongs to. On systems where group lookups are slow,
|
|
|
0e1944 |
- where users may belong to a large number of groups, and
|
|
|
0e1944 |
- where the number of groups listed in the _?s_?u_?d_?o_?e_?r_?s file
|
|
|
0e1944 |
- is relatively small, it may be prohibitively expensive
|
|
|
0e1944 |
- and running commands via s?su?ud?do?o may take longer than
|
|
|
0e1944 |
- normal. On such systems it may be faster to use the
|
|
|
0e1944 |
+ By default, s?su?ud?do?oe?er?rs?s will look up each group the user is
|
|
|
0e1944 |
+ a member of by group ID to determine the group name
|
|
|
0e1944 |
+ (this is only done once). The resulting list of the
|
|
|
0e1944 |
+ user's group names is used when matching groups listed
|
|
|
0e1944 |
+ in the _?s_?u_?d_?o_?e_?r_?s file. This works well on systems where
|
|
|
0e1944 |
+ the number of groups listed in the _?s_?u_?d_?o_?e_?r_?s file is
|
|
|
0e1944 |
+ larger than the number of groups a typical user belongs
|
|
|
0e1944 |
+ to. On systems where group lookups are slow, where
|
|
|
0e1944 |
+ users may belong to a large number of groups, and where
|
|
|
0e1944 |
+ the number of groups listed in the _?s_?u_?d_?o_?e_?r_?s file is
|
|
|
0e1944 |
+ relatively small, it may be prohibitively expensive and
|
|
|
0e1944 |
+ running commands via s?su?ud?do?o may take longer than normal.
|
|
|
0e1944 |
+ On such systems it may be faster to use the
|
|
|
0e1944 |
_?m_?a_?t_?c_?h_?__?g_?r_?o_?u_?p_?__?b_?y_?__?g_?i_?d flag to avoid resolving the user's
|
|
|
0e1944 |
- group IDs to group names and instead resolve all group
|
|
|
0e1944 |
- names listed in the _?s_?u_?d_?o_?e_?r_?s file, matching by group ID
|
|
|
0e1944 |
- instead of by group name. The _?m_?a_?t_?c_?h_?__?g_?r_?o_?u_?p_?__?b_?y_?__?g_?i_?d flag
|
|
|
0e1944 |
- has no effect when _?s_?u_?d_?o_?e_?r_?s data is stored in LDAP.
|
|
|
0e1944 |
- This flag is _?o_?f_?f by default.
|
|
|
0e1944 |
+ group IDs to group names. In this case, s?su?ud?do?oe?er?rs?s must
|
|
|
0e1944 |
+ look up any group name listed in the _?s_?u_?d_?o_?e_?r_?s file and
|
|
|
0e1944 |
+ use the group ID instead of the group name when
|
|
|
0e1944 |
+ determining whether the user is a member of the group.
|
|
|
0e1944 |
+
|
|
|
0e1944 |
+ Note that if _?m_?a_?t_?c_?h_?__?g_?r_?o_?u_?p_?__?b_?y_?__?g_?i_?d is enabled, group
|
|
|
0e1944 |
+ database lookups performed by s?su?ud?do?oe?er?rs?s will be keyed by
|
|
|
0e1944 |
+ group name as opposed to group ID. On systems where
|
|
|
0e1944 |
+ there are multiple sources for the group database, it
|
|
|
0e1944 |
+ is possible to have conflicting group names or group
|
|
|
0e1944 |
+ IDs in the local _?/_?e_?t_?c_?/_?g_?r_?o_?u_?p file and the remote group
|
|
|
0e1944 |
+ database. On such systems, enabling or disabling
|
|
|
0e1944 |
+ _?m_?a_?t_?c_?h_?__?g_?r_?o_?u_?p_?__?b_?y_?__?g_?i_?d can be used to choose whether group
|
|
|
0e1944 |
+ database queries are performed by name (enabled) or ID
|
|
|
0e1944 |
+ (disabled), which may aid in working around group entry
|
|
|
0e1944 |
+ conflicts.
|
|
|
0e1944 |
+
|
|
|
0e1944 |
+ The _?m_?a_?t_?c_?h_?__?g_?r_?o_?u_?p_?__?b_?y_?__?g_?i_?d flag has no effect when _?s_?u_?d_?o_?e_?r_?s
|
|
|
0e1944 |
+ data is stored in LDAP. This flag is _?o_?f_?f by default.
|
|
|
0e1944 |
|
|
|
0e1944 |
This setting is only supported by version 1.8.18 or
|
|
|
0e1944 |
higher.
|
|
|
0e1944 |
diff -up ./doc/sudoers.man.in.lookup ./doc/sudoers.man.in
|
|
|
0e1944 |
--- ./doc/sudoers.man.in.lookup 2017-04-25 13:17:51.074190108 +0200
|
|
|
0e1944 |
+++ ./doc/sudoers.man.in 2017-04-25 13:17:51.082190064 +0200
|
|
|
0e1944 |
@@ -2423,10 +2423,12 @@ This flag is
|
|
|
0e1944 |
by default.
|
|
|
0e1944 |
.TP 18n
|
|
|
0e1944 |
match_group_by_gid
|
|
|
0e1944 |
-By default, when matching groups,
|
|
|
0e1944 |
+By default,
|
|
|
0e1944 |
\fBsudoers\fR
|
|
|
0e1944 |
-will first resolve all the user's group IDs to group names and then
|
|
|
0e1944 |
-compare those group names to any group names listed in the
|
|
|
0e1944 |
+will look up each group the user is a member of by group ID to
|
|
|
0e1944 |
+determine the group name (this is only done once).
|
|
|
0e1944 |
+The resulting list of the user's group names is used when matching
|
|
|
0e1944 |
+groups listed in the
|
|
|
0e1944 |
\fIsudoers\fR
|
|
|
0e1944 |
file.
|
|
|
0e1944 |
This works well on systems where the number of groups listed in the
|
|
|
0e1944 |
@@ -2442,10 +2444,29 @@ running commands via
|
|
|
0e1944 |
may take longer than normal.
|
|
|
0e1944 |
On such systems it may be faster to use the
|
|
|
0e1944 |
\fImatch_group_by_gid\fR
|
|
|
0e1944 |
-flag to avoid resolving the user's group IDs to group names and
|
|
|
0e1944 |
-instead resolve all group names listed in the
|
|
|
0e1944 |
+flag to avoid resolving the user's group IDs to group names.
|
|
|
0e1944 |
+In this case,
|
|
|
0e1944 |
+\fBsudoers\fR
|
|
|
0e1944 |
+must look up any group name listed in the
|
|
|
0e1944 |
\fIsudoers\fR
|
|
|
0e1944 |
-file, matching by group ID instead of by group name.
|
|
|
0e1944 |
+file and use the group ID instead of the group name when determining
|
|
|
0e1944 |
+whether the user is a member of the group.
|
|
|
0e1944 |
+.sp
|
|
|
0e1944 |
+Note that if
|
|
|
0e1944 |
+\fImatch_group_by_gid\fR
|
|
|
0e1944 |
+is enabled, group database lookups performed by
|
|
|
0e1944 |
+\fBsudoers\fR
|
|
|
0e1944 |
+will be keyed by group name as opposed to group ID.
|
|
|
0e1944 |
+On systems where there are multiple sources for the group database,
|
|
|
0e1944 |
+it is possible to have conflicting group names or group IDs in the local
|
|
|
0e1944 |
+\fI/etc/group\fR
|
|
|
0e1944 |
+file and the remote group database.
|
|
|
0e1944 |
+On such systems, enabling or disabling
|
|
|
0e1944 |
+\fImatch_group_by_gid\fR
|
|
|
0e1944 |
+can be used to choose whether group database queries are performed
|
|
|
0e1944 |
+by name (enabled) or ID (disabled), which may aid in working around
|
|
|
0e1944 |
+group entry conflicts.
|
|
|
0e1944 |
+.sp
|
|
|
0e1944 |
The
|
|
|
0e1944 |
\fImatch_group_by_gid\fR
|
|
|
0e1944 |
flag has no effect when
|
|
|
0e1944 |
diff -up ./doc/sudoers.mdoc.in.lookup ./doc/sudoers.mdoc.in
|
|
|
0e1944 |
--- ./doc/sudoers.mdoc.in.lookup 2017-04-25 13:17:51.075190102 +0200
|
|
|
0e1944 |
+++ ./doc/sudoers.mdoc.in 2017-04-25 13:17:51.082190064 +0200
|
|
|
0e1944 |
@@ -2268,10 +2268,12 @@ This flag is
|
|
|
0e1944 |
.Em @mail_no_user@
|
|
|
0e1944 |
by default.
|
|
|
0e1944 |
.It match_group_by_gid
|
|
|
0e1944 |
-By default, when matching groups,
|
|
|
0e1944 |
+By default,
|
|
|
0e1944 |
.Nm
|
|
|
0e1944 |
-will first resolve all the user's group IDs to group names and then
|
|
|
0e1944 |
-compare those group names to any group names listed in the
|
|
|
0e1944 |
+will look up each group the user is a member of by group ID to
|
|
|
0e1944 |
+determine the group name (this is only done once).
|
|
|
0e1944 |
+The resulting list of the user's group names is used when matching
|
|
|
0e1944 |
+groups listed in the
|
|
|
0e1944 |
.Em sudoers
|
|
|
0e1944 |
file.
|
|
|
0e1944 |
This works well on systems where the number of groups listed in the
|
|
|
0e1944 |
@@ -2287,10 +2289,29 @@ running commands via
|
|
|
0e1944 |
may take longer than normal.
|
|
|
0e1944 |
On such systems it may be faster to use the
|
|
|
0e1944 |
.Em match_group_by_gid
|
|
|
0e1944 |
-flag to avoid resolving the user's group IDs to group names and
|
|
|
0e1944 |
-instead resolve all group names listed in the
|
|
|
0e1944 |
+flag to avoid resolving the user's group IDs to group names.
|
|
|
0e1944 |
+In this case,
|
|
|
0e1944 |
+.Nm
|
|
|
0e1944 |
+must look up any group name listed in the
|
|
|
0e1944 |
.Em sudoers
|
|
|
0e1944 |
-file, matching by group ID instead of by group name.
|
|
|
0e1944 |
+file and use the group ID instead of the group name when determining
|
|
|
0e1944 |
+whether the user is a member of the group.
|
|
|
0e1944 |
+.Pp
|
|
|
0e1944 |
+Note that if
|
|
|
0e1944 |
+.Em match_group_by_gid
|
|
|
0e1944 |
+is enabled, group database lookups performed by
|
|
|
0e1944 |
+.Nm
|
|
|
0e1944 |
+will be keyed by group name as opposed to group ID.
|
|
|
0e1944 |
+On systems where there are multiple sources for the group database,
|
|
|
0e1944 |
+it is possible to have conflicting group names or group IDs in the local
|
|
|
0e1944 |
+.Pa /etc/group
|
|
|
0e1944 |
+file and the remote group database.
|
|
|
0e1944 |
+On such systems, enabling or disabling
|
|
|
0e1944 |
+.Em match_group_by_gid
|
|
|
0e1944 |
+can be used to choose whether group database queries are performed
|
|
|
0e1944 |
+by name (enabled) or ID (disabled), which may aid in working around
|
|
|
0e1944 |
+group entry conflicts.
|
|
|
0e1944 |
+.Pp
|
|
|
0e1944 |
The
|
|
|
0e1944 |
.Em match_group_by_gid
|
|
|
0e1944 |
flag has no effect when
|