Skip to content
This repository has been archived by the owner on Jun 28, 2020. It is now read-only.

Script does not show users tried successfully used sudo su <username>, where <username> does not exists #4

Open
StrangeRanger opened this issue Jun 24, 2019 · 0 comments
Labels
fixable flaw a flaw in the script, that of which is not caused by the system itself, instead due to the script

Comments

@StrangeRanger
Copy link
Owner

StrangeRanger commented Jun 24, 2019

Describe the flaw
If a user inputs their sudo password correctly when executing sudo su <username>, but the username does not exist, they will still be marked as <username> has switched users <n> time(s).

Script type (main or cronjob version), which branch

Possible Solution
Unknown

@StrangeRanger StrangeRanger added the fixable flaw a flaw in the script, that of which is not caused by the system itself, instead due to the script label Jun 24, 2019
@StrangeRanger StrangeRanger added this to Pending priority and targeted script placing/grouping in Debian-10 via automation Jun 24, 2019
@StrangeRanger StrangeRanger removed this from Pending priority and targeted script placing/grouping in Debian-10 Jun 24, 2019
@StrangeRanger StrangeRanger added this to Pending priority and targeted script placing/grouping in Debian-Ubuntu via automation Jun 24, 2019
@StrangeRanger StrangeRanger moved this from Pending priority and targeted script placing/grouping to Cronjob specific in Debian-Ubuntu Jun 24, 2019
@StrangeRanger StrangeRanger moved this from Cronjob specific to Global/general in Debian-Ubuntu Jun 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
fixable flaw a flaw in the script, that of which is not caused by the system itself, instead due to the script
Projects
Debian-Ubuntu
  
Global/general
Development

No branches or pull requests

1 participant