It is only possible to run sudoedit on systems that  support  set‐
             ting the effective user‐ID.

       timed out reading password
             The  user  did not enter a password before the password timeout (5
             minutes by default) expired.

       you do not exist in the passwd database
             Your user‐ID does not appear in the system passwd database.

       you may not specify environment variables in edit mode
             It is only possible to specify environment variables when  running
             a command.  When editing a file, the editor is run with the user’s
             environment unmodified.

SEE ALSO
       su(1),  stat(2),  login_cap(3), passwd(5), sudo.conf(5), sudo_plugin(5),
       sudoers(5), sudoers_timestamp(5), sudoreplay(8), visudo(8)

HISTORY
       See    the    HISTORY.md    file    in     the     sudo     distribution
       (https://www.sudo.ws/about/history/) for a brief history of sudo.

AUTHORS
       Many people have worked on sudo over the years; this version consists of
       code written primarily by:

             Todd C. Miller

       See    the    CONTRIBUTORS.md    file    in    the   sudo   distribution
       (https://www.sudo.ws/about/contributors/) for an exhaustive list of peo‐
       ple who have contributed to sudo.

CAVEATS
       There is no easy way to prevent a user from gaining a root shell if that
       user is allowed to run arbitrary commands via sudo.  Also, many programs
       (such as editors) allow the user to run commands via shell escapes, thus
       avoiding sudo’s checks.  However, on most systems it is possible to pre‐
       vent shell escapes with the sudoers(5) plugin’s noexec functionality.

       It is not meaningful to run the ‘cd’ command directly via sudo, e.g.,

           $ sudo cd /usr/local/protected

       since when the command exits the parent process (your shell) will  still
       be  the  same.  The -D option can be used to run a command in a specific
       directory.

       Running shell scripts via sudo can expose the same kernel bugs that make
       set‐user‐ID shell scripts unsafe on some operating systems (if  your  OS
       has a /dev/fd/ directory, set‐user‐ID shell scripts are generally safe).

BUGS
       If you believe you have found a bug in sudo, you can submit a bug report
       at https://bugzilla.sudo.ws/

SUPPORT
       Limited  free  support is available via the sudo‐users mailing list, see
       https://www.sudo.ws/mailman/listinfo/sudo‐users to subscribe  or  search
       the archives.

DISCLAIMER
       sudo  is provided “AS IS” and any express or implied warranties, includ‐
       ing, but not limited to, the implied warranties of  merchantability  and
       fitness  for  a  particular  purpose are disclaimed.  See the LICENSE.md
       file distributed with  sudo  or  https://www.sudo.ws/about/license/  for
       complete details.

Sudo 1.9.14p2                    June 18, 2023                          SUDO(8)