Login not updating faillog
Also even if it were executable it would not be in the default paths so you would need to specify the full path or be in the /var/log directory to run it.
But I believe this is the database file not the command.
Hi guys, I am trying to enforce account lockouts after 3 failed attempts on ESX 4.0.
I have managed to get this working for the most part by adding the following line to /etc/pam.d/system-auth-generic: auth required pam_per_user deny=3 This allows me to enforce account lockouts for local logins, updating the /var/log/faillog file with the number of failed logins since the last successful one.
Thus I do not know where you get that from, but imho it is bogus.
I have such a file on 11.2 in /var/log sized 3.2K, but it is not marked executable.
Then have your MOTD grep that file for the current user.
I tried a touch command as recommended by one "expert" that posted a solution and the file changed from binary to text and is still 0 bytes in size? Are you talking about a tool named faillog that you want to execute? But then you talk about a file that is in the correct place, but you fail to tell where nor show any information about it.When I started to cover security I noted that the faillog command returned the command not found error when running as the root user.The file is in the correct place and is noted as a type "binary" but nothing can open it to get meaningful information, although kwrite will open it and shoe ASCII characters.However, I manage the ESX server via the v Sphere client and when supplying a bad password to this, the faillog is not updated.Strangely the accounts do still get locked out from vsphere after 3 failed attempts but they can still login via the terminal.
Search for login not updating faillog:
FINAL EDIT ( after OP found his own issue ) : If every new user can login, but after password change, login shows "Permission Denied", then check what what exacctly is changing, in /etc/passwd & /etc/shadow.