Failed Login Delay

Thaeris

So, quick note to nitpick:

Occasionally one has "mental flatulence" and then types in the wrong password. It then takes the computer a second or two to say, "no, try again," or however the GUI has been programmed. Perhaps the delay is just there to make an individual feel bad about their mistake or otherwise question their activities. But, it is odd, because the correct password registers immediately and you're ready to go very quickly otherwise.

...I think I've seen this behavior in both Windows and Solus. It does seem worse (by which I mean slower) in Solus, however...

TL;DR: Is there a way to eliminate the failed login delay in the OS? If not, is there a reason for the delay... which again seems strange as a successful login is basically immediate?!?

Harvey

It exists for security reasons without a delay brute forcing is much easier as it can burn through thousands of passwords a second.

There probably is a way to disable that delay but I do not know what it is nor do I recommend it.

Staudey

One place that delay is set is in /etc/login.defs

# Delay in seconds before being allowed another attempt after a login failure
# Note: When PAM is used, some modules may enforce a minimum delay (e.g.
#       pam_unix(8) enforces a 2s delay)
#
FAIL_DELAY		3

Could be that the display manager has an additional setting, and as the comment says PAM enforces its own delay.

In any case I'm with Harvey and would just leave it like that.

EbonJaeger

Huh. I had wondered about that myself years ago. Now I finally have an answer! TIL

Thaeris

You dudes are awesome! Thanks - I learned something on this one. As per the initial post, I figured the delay might have had some reason, but now I know for sure!