That way the user's editor config files are used by the editor.
While it is possible to preserve the value of the HOME environment
variable by adding it to the "env_keep" list in the sudoers file,
- doing so is strongly discouraged.
+ doing so is strongly discouraged. Users wishing to edit files
+ with sudo should run sudoedit (or sudo -e) to get their accustomed
+ editor configuration instead of invoking the editor directly.
Q) How can I keep sudo from asking for a password?
A) To specify this on a per-user (and per-command) basis, use the
.nr BA @BAMAN@
.nr LC @LCMAN@
.nr PS @PSMAN@
-.TH "SUDOERS" "@mansectform@" "June 20, 2019" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
+.TH "SUDOERS" "@mansectform@" "June 21, 2019" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
.nh
.if n .ad l
.SH "NAME"
Preserving the
\fRHOME\fR
environment variable has security implications since many programs use it
-when searching for configuration files.
+when searching for configuration or data files.
Adding
\fRHOME\fR
to
may enable a user to run unrestricted commands via
\fBsudo\fR
and is strongly discouraged.
+Users wishing to edit files with
+\fBsudo\fR
+should run
+\fBsudoedit\fR
+(or
+\fBsudo\fR \fB\-e\fR)
+to get their accustomed editor configuration instead of
+invoking the editor directly.
.SH "GROUP PROVIDER PLUGINS"
The
\fBsudoers\fR
.nr BA @BAMAN@
.nr LC @LCMAN@
.nr PS @PSMAN@
-.Dd June 20, 2019
+.Dd June 21, 2019
.Dt SUDOERS @mansectform@
.Os Sudo @PACKAGE_VERSION@
.Sh NAME
Preserving the
.Ev HOME
environment variable has security implications since many programs use it
-when searching for configuration files.
+when searching for configuration or data files.
Adding
.Ev HOME
to
may enable a user to run unrestricted commands via
.Nm sudo
and is strongly discouraged.
+Users wishing to edit files with
+.Nm sudo
+should run
+.Nm sudoedit
+(or
+.Nm sudo Fl e )
+to get their accustomed editor configuration instead of
+invoking the editor directly.
.El
.Sh GROUP PROVIDER PLUGINS
The