mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-22 01:49:11 +00:00
Code Issues Releases Wiki Activity

Add sudo.conf to SEE ALSO and rename section on sudo.conf

Browse Source
This commit is contained in:
Todd C. Miller 2014-11-11 14:18:07 -07:00
parent 328429832d
commit fbac05467b
3 changed files with 17 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/visudo.cat
View File

@ -83,18 +83,19 @@ DDEESSCCRRIIPPTTIIOONN
The various values have explicit types which removes much of
the ambiguity of the _s_u_d_o_e_r_s format.
UUssiinngg ssuuddoo..ccoonnff wwiitthh vviissuuddoo
DDeebbuuggggiinngg aanndd ssuuddooeerrss pplluuggiinn aarrgguummeennttss
vviissuuddoo versions 1.8.4 and higher support a flexible debugging framework
that is configured via Debug lines in the sudo.conf(4) file. Starting
with ssuuddoo 1.8.12, vviissuuddoo will also parse the arguments to the _s_u_d_o_e_r_s
plugin to override the default _s_u_d_o_e_r_s path name, UID, GID and file mode.
These arguments, if present, should be listed after the path to the
plugin (i.e. after _s_u_d_o_e_r_s_._s_o). Multiple arguments may be specified,
separated by white space. For example:
that is configured via Debug lines in the sudo.conf(4) file.
Starting with ssuuddoo 1.8.12, vviissuuddoo will also parse the arguments to the
_s_u_d_o_e_r_s plugin to override the default _s_u_d_o_e_r_s path name, UID, GID and
file mode. These arguments, if present, should be listed after the path
to the plugin (i.e. after _s_u_d_o_e_r_s_._s_o). Multiple arguments may be
specified, separated by white space. For example:
Plugin sudoers_policy sudoers.so sudoers_mode=0400
The following plugin arguments are supported:
The following arguments are supported:
sudoers_file=pathname
The _s_u_d_o_e_r_s___f_i_l_e argument can be used to override the default
@ -166,7 +167,7 @@ DDIIAAGGNNOOSSTTIICCSS
path name as the _s_u_d_o_e_r_s file to export.
SSEEEE AALLSSOO
vi(1), sudoers(4), sudo(1m), vipw(1m)
vi(1), sudo.conf(4), sudoers(4), sudo(1m), vipw(1m)
AAUUTTHHOORRSS
Many people have worked on ssuuddoo over the years; this version consists of

6
doc/visudo.man.in
View File

@ -233,7 +233,7 @@ The various values have explicit types which removes much of the
ambiguity of the
\fIsudoers\fR
format.
.SS "Using sudo.conf with visudo"
.SS "Debugging and sudoers plugin arguments"
\fBvisudo\fR
versions 1.8.4 and higher support a flexible debugging framework
that is configured via
@ -241,6 +241,7 @@ that is configured via
lines in the
sudo.conf(@mansectform@)
file.
.PP
Starting with
\fBsudo\fR
1.8.12,
@ -262,7 +263,7 @@ Plugin sudoers_policy sudoers.so sudoers_mode=0400
.RE
.fi
.PP
The following plugin arguments are supported:
The following arguments are supported:
.TP 10n
sudoers_file=pathname
The
@ -376,6 +377,7 @@ has the same path name as the
file to export.
.SH "SEE ALSO"
vi(1),
sudo.conf(@mansectform@),
sudoers(@mansectform@),
sudo(@mansectsu@),
vipw(@mansectsu@)

4
doc/visudo.mdoc.in
View File

@ -225,7 +225,7 @@ ambiguity of the
.Em sudoers
format.
.El
.Ss Using sudo.conf with visudo
.Ss Debugging and sudoers plugin arguments
.Nm visudo
versions 1.8.4 and higher support a flexible debugging framework
that is configured via
@ -233,6 +233,7 @@ that is configured via
lines in the
.Xr sudo.conf @mansectform@
file.
.Pp
Starting with
.Nm sudo
1.8.12,
@ -358,6 +359,7 @@ file to export.
.El
.Sh SEE ALSO
.Xr vi 1 ,
.Xr sudo.conf @mansectform@ ,
.Xr sudoers @mansectform@ ,
.Xr sudo @mansectsu@ ,
.Xr vipw @mansectsu@