I cannot use SUDO_ASKPASS anymore irathore@mygen2 ~ $ export SUDO_ASKPASS=/usr/lib64/misc/ssh-askpass irathore@mygen2 ~ $ sudo -A bash sudo: no askpass program specified, try setting SUDO_ASKPASS It does not matter what I set the SUDO_ASKPASS varable to, e.g. I will set it to a non-existant binary irathore@mygen2 ~ $ export SUDO_ASKPASS=/usr/lib64/misc/ssh-askpa irathore@mygen2 ~ $ sudo -A bash sudo: no askpass program specified, try setting SUDO_ASKPASS See above, it is same output (It should complain about (unable to run /usr/lib64/misc/ssh-askpa: No such file or directory) H E R E I D O W N G R A D E T O : sudo-1.8.4_p4 mygen2 portage # emerge =app-admin/sudo-1.8.4_p4 Now that I downgraded to 1.8.4_p4 irathore@mygen2 ~ $ export SUDO_ASKPASS=/usr/lib64/misc/ssh-askpa irathore@mygen2 ~ $ sudo -A bash sudo: unable to run /usr/lib64/misc/ssh-askpa: No such file or directory sudo: pam_authenticate: Conversation error Above shows that it is looking at $SUDO_ASKPASS Now I will set it to point to correct binary: irathore@mygen2 ~ $ export SUDO_ASKPASS=/usr/lib64/misc/ssh-askpass irathore@mygen2 ~ $ sudo -A bash Got a popup (entered my password) mygen2 irathore # Bingo!
new sudo version hooks getenv() which causes it to look only in the cleansed environment where SUDO_ASKPASS as removed. posted upstream to see how they want to fix it.
should be all set now in the tree; thanks for the report! Commit message: Version bump to fix SUDO_ASKPASS regression http://sources.gentoo.org/app-admin/sudo/sudo-1.8.5_p2.ebuild?rev=1.1
