(Draft) Lockscreen for Wayfire

[trigg]

GTK4 Lockscreen using session ext1.

Has a plugin-styled structure (but all plugins are compiled with it currently, and no external loading is done)

Plugins are individually togglable.

Plugins that can unlock the screen are:

• Password (Takes a string from user, runs it through PAM, unlocks if positive)
• Pin (has a pin pad GUI, takes a number of digits, hashes them, compares to users stored hash)
• Fingerprint (Interfaces with fprintd, on verification of previously enrolled fingerprint will unlock)
• Instant - disabled by default (A button, if pressed, unlocks)

Costmetic and functional plugins:

• Clock : show a date/time
• Battery: show battery, ups,charging status
• Volume Mute Toggle & Mic Mute Toggle
• MPRIS media control
• Username & Avatar image

TODO Plugins:

• Weather

• Yubikey/ U2F unlock

• Howdy (face recognition)

• Network status icon

Other TODO:

• Hide all plugins initially, when inactive hide/fade out again until user input
• Fade-in or pre-warn mode, which alerts the user to an impending lock.
• Background image, based on wf-background

Other notes:

Enabling PIN unlock requires creating a hash file:
echo -n "1234" | sha512sum | head -c 128 > ~/.config/wf-locker.hash
Obviously replacing the numbers quoted in the echo. Any above-zero number of digits is accepted. Writing non-digits into this will make it impossible to auth with PIN.
Fingerprint reader must have an enrolled finger to enable. It will also only accept the first one in the list of presented options.

Password has no 'submit' button as it is assumed the user has an enter/return at that point.

Plugins may enable/disable themselves in construction if it is expected to override the users choice. Notably : fingerprint reader disables itself without a device to read from, pin disables itself if the HASH is not found or is malformed.

It is possible for user to choose which part of the lockscreen a plugin displays in, but not the order of items. If you put all plugins into center-center of lockscreen then the plugins are shown top-to-bottom in alphabetical order. One option would be to sort the keys before we iterate on them in on_monitor_present.

[AKArien]

Haven't looked at the implementation yet, but from the description, if #121 were to be figured out and panel widgets were implemented as plugins, we would have access to quite a lot of functionality, and, in turn, all (bar the authentication) that is written for the lockscreen first could serve for the panel, no ?

[trigg]

I'm leaning heavily on existing panel widget code, but the factoring isn't similar enough to be able to use them 1:1.