Is there something I can do to expedite this? I submitted a bug that
wound up being a duplicate of this one, and even created and tested a
patch to the config. The config change is pretty trivial, and worked
perfectly in my testing. I'm not sure why this wouldn't be considered a
permanent fix rather than a workaround.
The fix is pretty trivia, and involves changing a default in the file
/usr/share/polkit-1/actions/net.reactivated.fprint.device.policy
to:
<action id="net.reactivated.fprint.device.enroll">
<description>Enroll new fingerprints</description>
.
.
.
<defaults>
<allow_any>no</allow_any>
<allow_inactive>no</allow_inactive>
<allow_active>auth_self_keep</allow_active>
</defaults>
The previous default was:
<allow_active>yes</allow_active>
Duplicate bug I created: https://bugs.launchpad.net/bugs/1901132
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532264
Title:
fprintd allows unauthorized root access
To manage notifications about this bug go to:
https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
