Bug#456015: gksu hangs when non-standard prompts are used.

[Timothy J. Miller]

Package: gksu
Version: 2.0.0-5

When a pam auth policy results in a different password prompt than gksu 
expects, the application hangs waiting for a sudo to provide a prompt it 
understands.

Observed with both pam_pkcs11 and pam_krb5.

Example (pam_pkcs11 is set as auth sufficient, with libcoolkeypk11 as 
the PKCS#11 module to enable smartcard use):

foobar at eeek:~$ gksu synaptic
Please insert your smart card or enter your username.
Smart card inserted.
Welcome OBSCURED.CERTIFICATE.COMMONNAME!

Note how it looks when sudo is used instead:

foobar at eeek:~$ sudo synaptic
Please insert your smart card or enter your username.
Smart card inserted.
Welcome OBSCURED.CERTIFICATE.COMMONNAME!
Smart card password:

Impact is severe on systems where smartcard or kerberos authentication 
is in use.  This bug prohibits gksu use entirely; user must use su and 
sudo at the command-line and cannot use any of the Gnome launchers built 
with gksu.

-- Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3505 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20071212/1f647f70/attachment.bin