Dean Fiala wrote:
>Since there is no bullet-proof solution, defense in depth should be
>your strategy.
>
>1) Use CAPTCHA as your first line
>2) Dynamically create the elements on your verification form with
>random names so that the crawlers have to be even smarter. Change the
>input field names and submit button name. Human users won't notice the
>difference.
>3) Add an email response verification link to fully activate the
>account, so the crawlers will be forced to use legimate email accounts
>4) Track the client IPs. If you notice a pattern of abuse block the
>offending IPs, or if you really want to drive them nuts, set up a
>honey pot that runs them slowly through an extra set of verification
>steps
>
>
>
5) Sign the email address they give up to as much spam as you can... ;)
Matt (feeling particularly evil tonight...)
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
