Red Hat Bugzilla – Bug 1548380
RFE: Create flag to filter to sudo -l output
Last modified: 2018-10-30 07:09:47 EDT
Currently the output of sudo -l is not parseable out of the box, and contains 3 different sections: - defaults for the host - defaults for the user - command that the user may run on the host Example of sudo -l output is: """ Matching Defaults entries for root on localhost: env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin, log_output, maxseq=150, iolog_dir=/var/log/sudo-io/%{user}, !requiretty Runas and Command-specific defaults for root: Defaults!/usr/bin/sudoreplay !log_output User root may run the following commands on localhost: (ALL : ALL) ALL """ It would be very useful to have the following flags as optional to "-l": --host-defaults --user-defaults --commands It should be also possible to combinate the options (ie: sudo -l --host-defaults --user-defaults) Example of the expected output: sudo -l --host-defaults """ Matching Defaults entries for root on localhost: env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin, log_output, maxseq=150, iolog_dir=/var/log/sudo-io/%{user}, !requiretty """ sudo -l --user-defaults """ Runas and Command-specific defaults for root: Defaults!/usr/bin/sudoreplay !log_output """ sudo -l --commands """ User root may run the following commands on localhost: (ALL : ALL) ALL """ sudo -l --host-defaults --user-defaults """ Matching Defaults entries for root on localhost: env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin, log_output, maxseq=150, iolog_dir=/var/log/sudo-io/%{user}, !requiretty Runas and Command-specific defaults for root: Defaults!/usr/bin/sudoreplay !log_output """
Upstream Tracker https://bugzilla.sudo.ws/show_bug.cgi?id=812
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3199