adding sudo #402
Merged
adding sudo #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is boh legit and absurd lol... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'll be honest... I know this seems silly - but I just observed a curious behavior by an asset discovery system which prompted me to document this.
The asset discovery system is running a command like
sudo sudo -p ************* lsof -iTCP -n -P -F pcnfTI think this might be an bug in their command generation... but then it occurred to me that if this command works it might be because of a rule like:
dev ALL=NOPASSWD: /usr/bin/sudoas opposed to the more expecteddev ALL=NOPASSWD: /usr/sbin/lsofor something.make me a sandwich -> access denied
sudo make me a sandwich -> access denied
sudo sudo make me a sandwich -> okay