-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pam-sshagent: only allow managed SSH keys #32178
Conversation
[Breaking change] Fixes #316
As I mentioned in #31611, I currently depend on the behavior as-is, so I would like this to be configurable. I also don't think the configuration being as it is now was an unintentional introduction, since it must have taken some work for @edolstra to come up with 3644f91 in the first place, which was necessary for this to work at all. I would be much happier with this patch if:
It's probably best if these both default to the more secure option, but it would be good to be consistent. What do you think? |
@matthewbauer ??? |
Sorry, I thought I was deleting branches on my own fork. |
Let's get this merged. Any objections? |
Reading #31611 (comment) I think this should be made configurable actually. |
I would say we go with #62317 to make it configurable properly. Thanks! |
[Breaking change]
Fixes #31611. If people have self-managed SSH keys in ~/.ssh, they will no longer be able to use those to get sudo access.
Update: This needs to be made configurable first, see the comment below. Basically, enable it if openssh non-managed keys are enabled, and allow overriding?