AussieDave
Banned User
- Joined
- Dec 24, 2005
- Location
- Australia
Hi all,
Got a bit of a problem and thought I'd run it past you guys (and girls) to ask if anyone can drop me some ideas how to fix this issue.
I have a member based section that is password protected. The user management script is php and it writes the users details to a database.
The issue...I have is a user who had their free membership declined and is now signing up with to multiple accounts.
Not that he can gain access because all applications are manually verified. However it's a pain in butt.
Although I can use a .htaccess file to block IP's or entire IP blocks it's useless in this situation because the user IP is dynamic. If I were to block the entire IP range I'd be block legitimate users too.
I had the idea of dropping a cookie into each peeps PC from the sign-up page. As only one registered user is allowed per PC/household I though this would be an affective way to stop this person abusing the registration form.
However the obvious flaw is if one deletes their cookies.
So if anyone has a better idea or some other suggestion to fix this problem I'd sure appreciate the input.
Cheers
Dave
Got a bit of a problem and thought I'd run it past you guys (and girls) to ask if anyone can drop me some ideas how to fix this issue.
I have a member based section that is password protected. The user management script is php and it writes the users details to a database.
The issue...I have is a user who had their free membership declined and is now signing up with to multiple accounts.
Not that he can gain access because all applications are manually verified. However it's a pain in butt.
Although I can use a .htaccess file to block IP's or entire IP blocks it's useless in this situation because the user IP is dynamic. If I were to block the entire IP range I'd be block legitimate users too.
I had the idea of dropping a cookie into each peeps PC from the sign-up page. As only one registered user is allowed per PC/household I though this would be an affective way to stop this person abusing the registration form.
However the obvious flaw is if one deletes their cookies.
So if anyone has a better idea or some other suggestion to fix this problem I'd sure appreciate the input.
Cheers
Dave