driver / standard (pull_request) Failing after 7s
driver / lint (pull_request) Successful in 20s
driver / types (pull_request) Successful in 1m8s
driver / test (3.12) (pull_request) Failing after 1m9s
driver / test (3.13) (pull_request) Failing after 1m3s
driver / lowest (pull_request) Failing after 33s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m8s
CI / driver (pull_request) Failing after 2m24s
driver / publish (pull_request) Skipped
A driver that typed `echo '<password>' | sudo -S -p "" <command>` into an interactive shell left that line, password and all, in the login user's shell history once per command, and where only the part before the first `&&` ran as root, files root should own were left to the login user. get_history_sudo_lines() counts the lines per history file with grep -c, as the login user, without reading any back. remove_history_sudo_lines() deletes exactly those lines with sed -i, overwrites the backup with shred -u, and as root gives the driver's SUDO_ROOT_FILES back to root:root where each is a regular file, not a link, owned by the login user. It reports each file's lines before and after. Nothing goes to stdin. The driver names the marker and the files and supplies run_command.