-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log number of OK keypresses #144
Comments
Thanks! Nice feature to implement! |
Exposed per key counts and statistics are potentially harmful; for example comparing key counts before and after a password entry (eg. asking someone to unlock their device twice). If #25 is not fixed this seems like less of an issue (only affecting non-password secrets). |
that's definitely something we should consider here. potential malware might rely on monitoring unshaky's log (which requires much lower permission than listening to key press itself) to log the keypress. |
Maybe make Shaky log available to root only, and require elevated privileges to look at per-key statistics. |
Unshaky does not require root permission to launch right now, I don't think it is worth to do this. |
Is your feature request related to a problem? Please describe.
I wonder what percentage of presses are shaky for each key. For example,
E
is at the top of my list, but that's probably because I use it a lotDescribe the solution you'd like
I wish Unshaky logged the number of all keypresses, both the overall total and totals for each key. Maybe the Statistics window could look something like:
And the dropdown could say, "Dismissed 25 shaky presses... (8.93% of 280)"
Describe alternatives you've considered
The table format and message text could change.
Additional context
N/A
The text was updated successfully, but these errors were encountered: