You are only browsing one thread in the discussion! All comments are available on the post page.

Return

Max_P ,
@Max_P@lemmy.max-p.me avatar

That’s managed by PAM: man.archlinux.org/man/faillock.8.en

I think it’s mostly intended for remote access like when SSH’ing in, it locks up after too many bad attempts.

When you have physical access a lot of security stops being relevant. Although for users with full disk encryption, that’d also force the attacker to wipe the keys in RAM so it’s still got some value.

penquin OP ,
@penquin@lemmy.kde.social avatar

How do I disable it? That link doesn’t show where to disable it. It just did it again and it’s driving my fucking insane. I literally didn’t do anything. I just locked my PC from the menu and went back to it to wake it up. I need this off my PC :/

NateSwift ,

Set nodelay in the config options. By default this should be in /etc/security/faillock.conf

penquin OP ,
@penquin@lemmy.kde.social avatar

Ok, I figured it out. Looks like this new mechanical keyboard I got does something when I wake the PC up that causes those 3 attempts to be triggered. So I just set deny = 0 in /etc/security/faillock.conf. And to be more sure, I set the unlock time to 0. Lol That was very stressful. Thank you for bringing up faillock.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • [email protected]
  • All magazines