Arch Linux

Cvlc

Member

Registered: 2020-03-26

Posts: 295

Re: [solved] default pam_faillock.so not being respected

No, not aware at all. I'm reading through it now, although not sure yet as to how it's related

This module is aimed at environments with central file servers that a user wishes to mount on login and unmount on logout, such as (semi-)diskless stations where many users can logon and where statically mounting the entire /home from a server is a security risk, or listing all possible volumes in /etc/fstab is not feasible.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,254

Re: [solved] default pam_faillock.so not being respected

Not only, eg. https://wiki.archlinux.org/title/Pam_mount#LUKS_volumes
Are you using systemd homed to carry around a $HOME among differently configured (different UID etc) systems or (only) for the randomly attached optional encryption?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Cvlc

Member

Registered: 2020-03-26

Posts: 295

Re: [solved] default pam_faillock.so not being respected

The ordering of the entries was reversed for https://bugs.archlinux.org/task/72967
Edit:
See also https://github.com/systemd/systemd/issu … -889130469

Sorry, I was away for a month without access to the laptop.

I think the systemd github link explains my issue, thanks !

From https://man.archlinux.org/man/homectl.1 :

--rate-limit-interval=SECS, --rate-limit-burst=NUMBER
Configures a rate limit on authentication attempts for this user. If the user attempts to authenticate more often than the specified number, on a specific system, within the specified time interval authentication is refused until the time interval passes. Defaults to 10 times per 1min.

I think that's what needed for my use case

Thanks for your help !