3 ms·
I have a pure software fix för this vulnerability: https://github.com/shapr/markovkeyboard https://github.com/shapr/markovkeyboard :-)
by shae 2y ago
I have a pure software fix för this vulnerability: https://github.com/shapr/markovkeyboard https://github.com/shapr/markovkeyboard
:-)
- TacticalCoder 2y agoThat's hilarious! Could work but I'd need the keys correspondence shown on the pic while typing: if physical 'f' key (on a QWERTY keyboard) is now 'p', I need to see "p/[f]" at the physical location of key 'f'. Then a nitpick: > "For example, if you type only "the" all day, then when you press the letter 't' the letter 'h' will be on the home row." 'h' is already on the home row on most keyboards.
- litenboll 2y ago> > "For example, if you type only "the" all day, then when you press the letter 't' the letter 'h' will be on the home row." > 'h' is already on the home row on most keyboards. For some reason this made me think about our unit tests at work :)
- gunapologist99 2y agofrequency analysis would probably fix your fix.
- pitaj 2y agoNot if it changes every sentence.