Support quiet Flag in pam.d Config#280
Open
DabeDotCom wants to merge 2 commits into
Open
Conversation
Example: **`/etc/pam.d/ssh`** ``` auth sufficient pam_duo.so quiet ```
DabeDotCom
force-pushed
the
pam-quiet
branch
from
9837f96 to
eb208e9
Compare
Author
|
Bump? This and #310 should be pretty benign, but they're enough of a "Pebble In My Shoe" that I went ahead and fixed them... It'd be nice if they got reviewed/merged, just so I wouldn't have to maintain my own fork any more. Thanks! :-D |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Example:
/etc/pam.d/sshSummary of the change
A trivial update that allows admins to silence
pam_info()messagesTest Plan
I added two simple tests:
pam.dparser accepts thequietflagquietflag actually does silence the output «grin»PS: I also added the flag to the
pam_duo(8)manpage.