On Thu 14 Aug 2008, Jamie Zawinski wrote: > But the message goes away if you just click the mouse, right?
Hmm, it does; but the delay is just long enough to be irritating, but just short enough that it almoast takes me longer to reach for the mouse and click. If the message disappears just before I click, I might end up closing a window or so if I'm unlucky enough to click the X... > It is annoying that dismissing the unlock dialog without typing anything > (or just timing out) counts as a failed login, but that's PAM > braindamage. > > If the user times out, or hits ESC or Cancel, the xscreensaver > 'pam_conversation' state machine returns PAM_CONV_ERR, and PAM logs that > as an authentication failure, even though there was no attempt to > present a password. I wish there was some way to indicate that this was > a "cancel" rather than a "fail", so that it wouldn't show up in syslog, > but I don't think there is. I think the only options I have available > are PAM_SUCCESS and PAM_CONV_ERR. (I think that PAM_ABORT means > "internal error", not "cancel".) The timeout is implemented within the xscreensaver code, right? So surely xscreensaver "knows" whether there's a timeout. Hence it can act appropriately in such a case. I'd have thought that the PAM stuff would only be accessed after the user hits enter, so PAM shouldn't be involved unless it was a real login attempt. At least, that's how I would have programmed it... Anyways, I'm sure the warning message is put there by xscreensaver. Hence a config option should be able to prevent it from ever appearing; as I said, I couldn't care less. Or make the config value the duration of the message, where 0 means "go away immediately", that would be fine too. thanks, Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
