| 1:39 pm on Sep 2, 2004 (gmt 0)|
Signs welcome to WebmasterWorld!
It does not look as though there is any security being used for the password (IE MD5). This means you should be able to simply get the username and password out of the database admin.
| 1:47 pm on Sep 2, 2004 (gmt 0)|
well maybe i can use a htpassw...
But whats the problem with the script? Does it works?
| 1:52 pm on Sep 2, 2004 (gmt 0)|
I have no idea I didnt install it. I simply looked for you a way to get the username and password from the admin database. If you get that username and password and it still wont let you log in then I would say it doesnt work and ask for a refund.
| 1:59 pm on Sep 2, 2004 (gmt 0)|
well i just bought it for € 1,30...and i think that if you re-encoded it, it will be more than € 1,30 :)
| 2:01 pm on Sep 2, 2004 (gmt 0)|
| 2:06 pm on Sep 2, 2004 (gmt 0)|
Yeah someone had placed this script on a site and you can buy it for € 1,30 through the mobile phone
| 2:56 pm on Sep 2, 2004 (gmt 0)|
Welcome signs. First some questions.
1. how do you know that the username and password are valid?
2. are you typing in the right case?
3. did you modify the login script at all?
| 4:43 pm on Sep 2, 2004 (gmt 0)|
I can check the username and password in the MySQL database.
No i haven't modify the login script. It is in the original state
| 4:50 pm on Sep 2, 2004 (gmt 0)|
I often find issues with hashed values in pre-loaded scripts. It comes down to how the password was encrypted during INSERT or UPDATE to the table.
A quick work around is to just get to a command line and update the password in the database or, if the author used PHP, write a quick script to get the job done. Of course, you'll have to have a peek inside the author's code to find the password update or insert routine and use the same SQL code you find in the script. For example, if the author used PHP's md5 function, you need to do the same.