Huh, I thought we had a different bug about this, but I can't find it
now.
I just wanted to note here that we found that pam_tally2 didn't have
enough reporting to be useful to us. It couldn't tell the greeter (A)
how many attempts were left to go or (B) when it was causing a punitive
delay (vs a PAM delay for some other reason -- though the greeter could
probably guess after a few seconds).
So we went with a tally kept in AccountsService. If we later figure out
how to take more advantage of pam_tally2, we can always change backends.
Losing existing tallies isn't a big deal.
** Changed in: ubuntu-touch-session (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348251
Title:
please make use of pam_tally2 for Touch login and screenunlock
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1348251/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
