greeter unlock configuration
Bug #1218010 reported by
Sebastien Bacher
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-system-settings |
Fix Released
|
Undecided
|
Iain Lane | ||
ubuntu-system-settings (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The design has options to set the greeter unlock to:
- swipe
- 4 digits
- passphrase
notes from a discussion with mterry on how to do that
"You call it like /usr/lib/
and pass in "PASSWORD\nPIN" via stdin
you can skip PIN to unset a pin
But PINs still need a password underneath
...
so swipe is simply normal "user doesn't need a password" stuff. Like put them in nopasswdlogin group etc
passphrase is you do above, pass in a passphrase
4digit can just be passing in 4digit\n4digit I suppose. If you didn't want to have a backing password"
Related branches
lp://staging/~laney/ubuntu-system-settings/security-privacy-set-security-demo
- Sebastien Bacher (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 500 lines (+140/-65)6 files modifiedplugins/battery/PageComponent.qml (+6/-4)
plugins/security-privacy/LockSecurity.qml (+70/-47)
plugins/security-privacy/PhoneLocking.qml (+9/-8)
plugins/security-privacy/securityprivacy.cpp (+39/-1)
plugins/security-privacy/securityprivacy.h (+16/-0)
schema/com.ubuntu.touch.system-settings.gschema.xml (+0/-5)
Changed in ubuntu-system-settings: | |
assignee: | nobody → Iain Lane (laney) |
Changed in ubuntu-system-settings: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In addition... Until we split out the greeter into a proper LightDM greeter, we have a goofy, insecure, demo method of setting password/pin:
Edit/Create the file ~/.unity8- greeter- demo with the following syntax:
[General]
passwordValue=4890
password=pin
Where password can be "none", "pin", or "keyboard". And passwordValue is either the PIN value or passphrase, depending on the type of password.
Obviously, this is just a temporary solution, but it should be easy to implement in the meantime and will get the UI to work until we have a proper split.