You are not logged in.
Pages: 1
Hello everyone I have a problem. Arch has decided to block my account for some reason and does not want to unlock it back. I can't even use "sudo pacman -Syu" because I need to enter the password, and it won't accept it.
Wherever I enter the password, in the graphical settings interface, in the terminal for sudo, it does not accept the password and says that the account is blocked for 10 minutes. I've been waiting for almost an hour and a half, but as soon as 10 minutes run out, new 10 minutes immediately appear from somewhere and I have to wait again. At the same time, I did not make mistakes when entering the password even once.
I tried using the terminal that appears when Ctrl+ Shift + F4, but it won't let me log in there either. It says that this account is blocked for X minutes, and when you enter the password, it says login incorrect
Please help me, I urgently need sudo, but I can't get access to it xd
Last edited by flowerpower (2024-06-07 21:43:11)
Offline
https://wiki.archlinux.org/title/Securi … n_attempts
You're probably running some sudo invocation in a non-interactive shell (cronjob etc) that triggers this?
Offline
Nah, I don't
Even if I do, I have rebooted like 4 times, I think this would kill the process.
I tried to enter "faillock --user ...." but it did nothing. I saw on other forum, that I need to run faillock as root, but I can't lol
Offline
No you don't - what's the output of
faillock
sudo -lOffline
flwrpwr@archlinux ~> faillock
flwrpwr:
When Type Source Valid
2024-06-08 00:11:12 SVC sudo V
2024-06-08 00:11:12 SVC sudo V
2024-06-08 00:11:13 SVC sudo V
flwrpwr@archlinux ~>
flwrpwr@archlinux ~> sudo -l
[sudo] password for flwrpwr:
Try again.Last edited by flowerpower (2024-06-07 21:26:16)
Offline
Please use [code][/code] tags. Edit your post in this regard.
"sudo -l" should™ not require credentials?
However, there're currently three failed logins and the account is locked by faillock because of that
faillock --reset
faillock --reset
sudo -lOffline
faillock --reset didn't work
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What's the resulting faillock list?
faillock --reset
faillock # sorry for the copypasta
sudo -lOffline
flwrpwr@archlinux ~> faillock --reset
flwrpwr@archlinux ~> faillock
flwrpwr:
When Type Source Valid
2024-06-08 00:30:38 SVC sudo V
2024-06-08 00:30:38SVC sudo V
2024-06-08 00:30:38 SVC sudo V
flwrpwr@archlinux ~>
flwrpwr@archlinux ~> sudo -l
[sudo] password for flwrpwr:
Try again.Same as before...
Offline
There're three new faillock entries from the exact same second - something's calling sudo at a high pace. You need to stop that.
You can also disable faillock (see the wiki), but that will require root permissions, ie. in doubt you'll have to do this by chrooting into the system from a live iso boot.
The correct approach however is to stop the bogus sudo calls.
Last edited by seth (2024-06-07 21:36:39)
Offline
I realized a thing
flwrpwr@archlinux ~> faillock
flwrpwr:
When Type Source Valid
2024-06-08 00:30:38 SVC sudo V
2024-06-08 00:30:38 SVC sudo V
2024-06-08 00:30:38 SVC sudo V
flwrpwr@archlinux ~> faillock --reset
flwrpwr@archlinux ~> faillock
flwrpwr:
When Type Source Valid
2024-06-08 00:35:52 SVC sudo V
2024-06-08 00:35:52 SVC sudo V
2024-06-08 00:35:53 SVC sudo V"faillock --reset" adds a failed login attempts
Offline
No, some "sudo" call does. You just get new entries because of the reset but this is gonna be some background script going wild.
Offline
TOTAL BRUH
Conky is guilty
I think that its config, that I pasted from another user, causes a problem
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Yeah, thank you!
Offline
Pages: 1