** Changed in: unity
Milestone: None => 7.2.1
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Also affects: unity/7.3
Importance: Undecided
Status: New
** No longer affects: unity/7.3
** Changed in: unity
Milestone: 7.2.1 => 7.3.0
** Changed in: unity/7.2
Milestone: None => 7.2.1
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Assignee: (unassigned) => Andrea Azzarone (andyrock)
** Changed in: unity-greeter (Ubuntu)
Assignee: Andrea Azzarone (andyrock) => (unassigned)
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Andrea Azzarone (andyrock)
** Changed in: unity/7.2
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1305440
Title:
Allow a distinct pam config file for greeter and for lock-screen
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in “unity” package in Ubuntu:
In Progress
Status in “unity-greeter” package in Ubuntu:
Invalid
Bug description:
It might be desirable to have a distinct pam config file when logging
in and when unlocking the screen. Specifically, using a fingerprint
reader is fine for sudo or for unlocking, but you want to use your
password when logging in, to provide a secret and be able to unlock
the gnome-keyring for example.
See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
pam-config-in-the-lockscreen
So this feature request is about allowing for a (optional) pam config
file for the lock-screen, distinct from the /etc/pam.d/lightdm
currently used and shared with the greeter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1305440/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
