Version: , by Scott MacVicar
Developer Last Online: Mar 2016
Version: 2.2.x
Rating:
Released: 11-23-2001
Last Update: Never
Installs: 41
No support by the author.
This is a hack that was suggested by paulomt1, all it does is log failed logins and stores them in a table. An admin can then look at the failed logins in the admin panel, searching based on ip, username, password or date. They can also prune the old logs to save space.
You will be required to create a table this can be done via phpmyAdmin or the hack by Firefly which allows you to run queries via the admin panel. You then have to edit member.php to add the query to insert the failed login information and /admin/index.php to add the links to the loginlog.php file.
Updated 25th November 2001 @ 22:15
Added additions suggested by Mike to the file. Instructions on how to upgrade from the pervious version of this hack is included within install.txt, you will need to run 2 sql queries to adjust the table, adjust the line in member.php and upload loginlog.php again to complete the upgrade.
Scott
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
ok Mike i can see why you would add resolve IP and if its ok I'll add that to loginlog.php but the link to edit the members profile I don't understand. Why do you need to check for failed logins then go to edit the member info?
[QUOTE]Originally posted by PPN ok Mike i can see why you would add resolve IP and if its ok I'll add that to loginlog.php but the link to edit the members profile I don't understand. Why do you need to check for failed logins then go to edit the member info?
* Log into phpMyAdmin
* Click in the menu on the left on the database you want to open
* In the screen on the right, scroll down untill you see: Run SQL query/queries on database <database-name>
* Copy the entire bit from the install txt file starting with: CREATE TABLE
and ending with: );
and paste it into the text field below the Run SQL query
* Click go, and you'll have your loginlog table
So far we have had 66 failed logins tries.
About 20 of them are by one member, who was banned, but thought he had forgotten his password or something. So sad...
Anyway, while looking at these logins it occurred to me that all of these passwords they're trying are probably passwords they use on other sites.
Just a thought.
yeah I thought of this hoped that limiting it to trusted admins would minimise this, they had access to see users passwords before 2.2.x
I didn't plan it on someone who was banned trying passwords, I was thinking of people trying to brute force accounts.
Reports for my forums are
6 failed logins
4 were for admin users and 2 was someone trying to guess a password.