Keyboard Privacy
Overview
Keyboard Privacy is a Chrome extension developed by Urity Group.
According to the data from Chrome web store, current version of Keyboard Privacy is 2.7, updated on 2019-10-31.
3,000+ users have installed this extension.
24 users have rated this extension with an average rating of .
Prevents behavioral profiling by randomizing the rate at which characters reach the DOM.
Prevents behavioral profiling by randomizing the rate at which characters reach the DOM.
v2.7
Updated 30/10/19:
Updated to reflect changes in the industry and ensure every type of input is protected.
v2.5
Updated 20/08/16:
Fixed lag caused by numerous textarea inputs on a given page.
Increased default "dwell" and "gap" times to 200ms.
Tested against BehavioSec 20/08/16 with a 0.02% (RED) result.
Notice:
This is a proof-of-concept plugin, following research by two independent security professionals (Paul Moore & Per Thorsheim). See https://paul.reviews/behavioral-profiling-the-password-you-cant-change/ for more details.
Keyboard Privacy Alternatives
Latest Reviews
See More
Sylvain
2020-07-01
This seems to work @ 300ms on Keytrack but they were able to get high confidence @ 200ms for me. The Experimental port on Mozilla Addons does not work at all for me however, any chance you can finally port this to Firefox, now that they have a decent WebExtension API? |
A Google User
2018-06-12
It's great stuff, super interesting. |
mytransceiver
2017-11-20
No, as of 2017 Nov, all the "biometric" can over come this tiny trick with over 90% confidence. Even 1000 dwell/delay would not help at all. |
Franco GR
2017-05-25
I've been using this extension for quite a while, both in Firefox and Chrome. It's great. |
Puppette Master
2016-07-30
With the add-on disabled, converged on a green policy for the id; during testing of the trained id, needed to set add-on to 500 each dwell/delay to confuse the tested id to red reliably. Full training with the add-on enabled at 500 dwell/delay each still converged on a green id policy; also, it still recognized the id during testing with or without the add-on enabled at 500. Full training with add-on at 1000 each converged on a red policy during training, yellow policy during testing, yellow or red identification; during testing, did not matter with or without add-on |