Pattern unlocking

[Tej Shah]

At least for my use case, having the same PAM module for ssh, keyboard and
pattern is fine because most of my users will never actually use anything
else outside the touchscreen. So they don't really have to know that the
nodes actually correspond to different letters. The letters are just for
generating the string that will be inputted to the greeter.

How about this, I can make a QML Component(s) that will simply return back
a string based on the pattern. Would that be useful for anybody? Also, will
it be a problem if I release it as GPL v3?


On Fri, Jun 14, 2019 at 2:30 PM David Edmundson <david at davidedmundson.co.uk>
wrote:

> As a demo it's fine, and you get to make the UI in parallel. So go for it.
>
> In terms of formatting into a string for use with pam_response, that
> seems sensible.
>
> For deployment it's a bit sketchy if you use the same auth for ssh or
> whatever. You'd probably want to have two different PAM modules so we
> use the different auth checks for different things.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-mobile/attachments/20190614/76fbf237/attachment.html>