Bug 2084528
| Summary: | pam_ssh_agent_auth is working with sudoedit but not with sudo | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | percy |
| Component: | openssh | Assignee: | Dmitry Belyavskiy <dbelyavs> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 36 | CC: | crypto-team, dbelyavs, dwalsh, jjelen, lkundrak, mattias.ellert, tm |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-25 15:51:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
percy
2022-05-12 11:21:00 UTC
Does using the following work? sudo -E echo test Do you have the following line in your /etc/sudoers ? Defaults env_keep += "SSH_AUTH_SOCK" *** Bug 2084527 has been marked as a duplicate of this bug. *** Behavior of sudo with -E switch seems to be no different. Currently I do not have such a line in /etc/sudoers since man for pam_ssh_agent_auth advises it is required only for older OSes however I've started my tests with that line configured. correction: with sudo -E it seams to work both with local system and over ssh: maj 13 06:01:48 host sudo[34513]: Beginning pam_ssh_agent_auth for user user maj 13 06:01:48 host sudo[34513]: Attempting authentication: `user' as `user' using /home/user/.ssh/authorized_keys maj 13 06:01:48 host sudo[34513]: Contacted ssh-agent of user user (1000) maj 13 06:01:48 host sudo[34513]: trying public key file /home/user/.ssh/authorized_keys maj 13 06:01:48 host sudo[34513]: auth_secure_filename: checking for uid: 1000 maj 13 06:01:48 host sudo[34513]: secure_filename: checking '/home/user/.ssh' maj 13 06:01:48 host sudo[34513]: secure_filename: checking '/home/user' maj 13 06:01:48 host sudo[34513]: secure_filename: terminating check at '/home/user' maj 13 06:01:48 host sudo[34513]: matching key found: file/command /home/user/.ssh/authorized_keys, line 1 maj 13 06:01:48 host sudo[34513]: Found matching ECDSA-SK key: SHA256:/key/ maj 13 06:01:51 host sudo[34513]: Authenticated (agent): `user' as `user' using /home/user/.ssh/authorized_keys Because the documentation is wrong. It is already updated in upstream, but not yet in Fedora: https://github.com/jbeverly/pam_ssh_agent_auth/pull/29/files I am not sure when we will have a new upstream release, but this can be fixed as a backport of documentation to prevent confusing users. Even better solution would be if the pam_ssh_agent_auth dropped this snippet into the /etc/sudoers.d/ directory so the users would not have to bother with this. The file is in the repository, with the template, but it is not installed: https://github.com/jbeverly/pam_ssh_agent_auth/blob/master/pam_ssh_agent_auth.sudoers.conf This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |