I was trying to use pam_ssh_agent_auth module to authorize sudo, but hit a pretty nasty issue. It seems that at the time sudo launches pam check, it doesn't have any environment variables set, except for USER, PATH, HOME, LOGNAME and LDAPNOINIT. And definitely no SSH_AUTH_SOCK. As far as I understood from sudo source code (I can be wrong though), it's not some kind of configuration thing, sudo just flushes all the environment and re-creates it later.
I was wondering, if anyone had luck with this software on CentOS 5.3 and sudo 1.6.8p12, or if I'm missing something here?
Many thanks!
Denis.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello!
I was trying to use pam_ssh_agent_auth module to authorize sudo, but hit a pretty nasty issue. It seems that at the time sudo launches pam check, it doesn't have any environment variables set, except for USER, PATH, HOME, LOGNAME and LDAPNOINIT. And definitely no SSH_AUTH_SOCK. As far as I understood from sudo source code (I can be wrong though), it's not some kind of configuration thing, sudo just flushes all the environment and re-creates it later.
I was wondering, if anyone had luck with this software on CentOS 5.3 and sudo 1.6.8p12, or if I'm missing something here?
Many thanks!
Denis.
Oh, it seems to work with sudo 1.6.9p17. Looks like sudo guys changed code that does environment stuff in 1.6.9.