Hello !
I may have a technique you can use for this. However I would use caution since it seems to me that Coppermine is designed to let users vote anonymously. At least warn your users that you could use this information in case of suspected trickery.
Ok, this is how it worked for me.
This is no online feature so you must have access to your database.
Steps:
1. Idendify the record where the suspicious vote is cast in the database. In my case I could track it to the given picture or at the last record sorted by date.
In my database the table containing the voting data is called "cpg11d_votes". I could for instance use mysql to query a given image:
select * from cpg11d_votes where pic_id=3661;
this would bring up something like:
+--------+----------------------------------+------------+
| pic_id | user_md5_id | vote_time |
+--------+----------------------------------+------------+
| 3661 | 045117b0e0a11a242b9765e79cbf113f | 1157617785 |
| 3661 | 062ddb6c727310e76b6200b7c71f63b5 | 1157701251 |
| 3661 | 0771fc6f0f4b1d7d1bb73bbbe14e0e31 | 1157358193 |
| 3661 | 0c6b6f19684ed9b6ff07575fcf81c98d | 1157652012 |
2. The output from 1.) shows the image voted on, the time of the vote and the userID hashed with the MD5 algorithm.
But since the userID is MD5 hashed i used this site to reverse the hash to get the real ID:
http://md5.rednoize.com/From there I could get the real userId.
3. I now have the userID, but who is this really ?
In my system, we have bridged the Coppermine to the SMF forums. so the corresponding userID would be stored in the "<something>_members" table.
I could query the SMF forum users table this way:
select * from dforum_members where ID_MEMBER=1077;
"1077" was the result of the MD5 reversal.
So thats it.
This technique was used on
http://www.dykkesiden.com.
/twistah