Brian J. Tarricone
49394b3e53
Previously I was just presenting a static username/password box, and then running PAM with pre-set credentials. This works just fine when PAM is expecting a username and password, but if it's expecting something like a fingerprint scan or a hardware security token, this wouldn't entirely work right. Well, it would "work", but the username/password dialog would be displayed, and then hitting "Unlock" would start a different auth process with no visible feedback as to what's supposed to happen. This also means I need to switch PAM wrapper crates; the one I was using before did not allow passing a fixed username to the underlying pam_start() call, which meant that PAM would try to prompt the user for it, which is not what we want.
30 lines
806 B
Plaintext
30 lines
806 B
Plaintext
Source: bscreensaver
|
|
Maintainer: Brian Tarricone <brian@tarricone.org>
|
|
Section: x11
|
|
Priority: optional
|
|
Standards-Version: 3.9.2
|
|
Build-Depends:
|
|
debhelper (>= 13),
|
|
pkg-config,
|
|
libxcb-randr0-dev,
|
|
libxcb-xfixes0-dev,
|
|
libxcb1-dev,
|
|
libxkbcommon-x11-dev,
|
|
libgtk-3-dev,
|
|
libpam0g-dev,
|
|
cargo (>= 0.57),
|
|
rustc (>= 1.58),
|
|
clang,
|
|
help2man
|
|
|
|
Package: bscreensaver
|
|
Architecture: any
|
|
Depends: ${shlibs:Depends}, ${misc:Depends}
|
|
Description: secure X11 screen locker
|
|
BScreensaver is a privilege-separated screen locker that attempts to
|
|
be as secure as possible, meaning that a crash one one of its
|
|
non-critical components will not cause the screen to unlock.
|
|
.
|
|
It is fairly barebones so far, and only supports blanking the screen.
|
|
There is a single unlock dialog implementation that uses GTK3.
|