Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

What's the point of faillock?

+4
−0

On a default Arch install, faillock makes it so that if you enter the sudo password wrong too many times, even the correct password will be rejected until the timer is up.

At the same time, you can type faillock --reset without sudo and reset the timer.

What is the point of this?

I can see a dubious security benefit to not giving people too many guesses. But there is already a delay when you type a wrong password, so it's not like they can brute force it. And if your password is so easy that a few guesses are enough... Well, they can just wait 5 minutes and guess anyway.

Is there some logic to why it gets set up in this silly way? I know Arch doesn't customize packages, but the author of faillock must have had some kind of reason. Is there some security advantage to enabling this failed password timeout, but leaving faillock --reset runnable without knowing the password?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

0 answers

Sign up to answer this question »