@rodstartube yeah you're right - I should have, but it was a lazy quick fix. the video was just a quick demonstration of an idea I had using some parts I had lying around, obviously not a finished product
@uwadb So, if the user remains the key pressed more than your delay, it will read 2 or more key presses? that is bad. To prevent as you say "sending the same key multiple times by accident", you should add the "pressed Key" just after a "released Key" variable, that way no matters the time the user holds the key pressed. If you want to prevent as you say "bruteforce attempts" you could add a delay (annoying if you want) just after password checking.-
@rodstartube I added a half second delay as a simple fix to prevent sending the same key multiple times by accident. this will also help to prevent bruteforce attempts, as it'll take 4 seconds per try
@rodstartube yeah you're right - I should have, but it was a lazy quick fix. the video was just a quick demonstration of an idea I had using some parts I had lying around, obviously not a finished product
uwadb 10 months ago
@uwadb So, if the user remains the key pressed more than your delay, it will read 2 or more key presses? that is bad. To prevent as you say "sending the same key multiple times by accident", you should add the "pressed Key" just after a "released Key" variable, that way no matters the time the user holds the key pressed. If you want to prevent as you say "bruteforce attempts" you could add a delay (annoying if you want) just after password checking.-
rodstartube 10 months ago
@rodstartube I added a half second delay as a simple fix to prevent sending the same key multiple times by accident. this will also help to prevent bruteforce attempts, as it'll take 4 seconds per try
uwadb 10 months ago
that is a crappy delay (keypress vs LCD display), any reason, any problem, bad design??
rodstartube 10 months ago