fix: restore lock screen U2F/fingerprint auth to working state#2052
fix: restore lock screen U2F/fingerprint auth to working state#2052Purian23 merged 2 commits intoAvengeMedia:masterfrom
Conversation
|
Hi there, thanks for looking into it. We'll do the same on our end as the changes that fixed yours previously, broke others which led to what we hoped would be general updates to work for everyone. |
…bility - Restores SettingsData for fingerprint/U2F, keeping lock screen and New Greeter Settings UI in sync
|
Hey @xPathin give the updated commit a try. Some of the settings you reverted are not on the Stable branch of DMS v1.4.4, but are in the Master branch. We have a brand New Greeter UI for settings that I want to keep in sync with the LockScreen. Otherwise I think what you updated along with the changes in place should resolve both issues. |
Thank you, all working for me! |
* fix: restore lock screen U2F/fingerprint auth to working state * fix(pam): Keep SettingsData as single source of truth for auth availability - Restores SettingsData for fingerprint/U2F, keeping lock screen and New Greeter Settings UI in sync --------- Co-authored-by: purian23 <purian23@gmail.com>
Summary
Pam.qmlintroduced between185284d4ande86227f0that broke FIDO2/U2F security key support on the lock screen/etc/pam.d/loginwatcher that overrides bundled U2F config)message.toLowerCase().includes("touch")instead ofmessage !== "")Fixes #2050
Test plan