Hi Niall,
yes, we are using it in the registration process, but there are already a lot of bots able to solve it. Sometimes when too many get through, we switch to asking questions and compare the text answers to a list. But some get through those, too. As the spammer, you can even book services, where you use an api to query your way in and there are humans clicking through the process and build a list of possible answers that are then used automatically.
There are those bots trying to register and spam us and there are those trying to brute force their way into our wordpress website and forum with scanning it for member names and launching dictionary attacks on their passwords, trying to hack the accounts.
I hope everyone here has a secure password, not just a simple word? (nudge nudge)
Then there are the AIs and search engines gathering all kinds of information that are spidering our forum. Some behave well and follow our definition file for those.
There are numbers of requests per minute and what not to index and all of those information in it.
Some are behaving very badly and bomb us with several 100 requests per second.
Some are just bad folks, running (D)DOS attacks to shut down the service.
Some of all the above are easy to catch, some not. Some hide behind anonymizers and come from a variety of different IP addresses.
There is the risk of getting through and logging in as individuals, spam us, gather private information or even passwords and accounts, they then try on other sites.
There needs to be a balance of security measures and expenditure of time and usability, too.
And we don't want to lock out members and the well behaving AIs and search engines, either.
A big issue is that all the above combined produces such a huge load on our server that it is not usable for us any more.
Gassho,
Kotei sat/lah today.
yes, we are using it in the registration process, but there are already a lot of bots able to solve it. Sometimes when too many get through, we switch to asking questions and compare the text answers to a list. But some get through those, too. As the spammer, you can even book services, where you use an api to query your way in and there are humans clicking through the process and build a list of possible answers that are then used automatically.
There are those bots trying to register and spam us and there are those trying to brute force their way into our wordpress website and forum with scanning it for member names and launching dictionary attacks on their passwords, trying to hack the accounts.
I hope everyone here has a secure password, not just a simple word? (nudge nudge)
Then there are the AIs and search engines gathering all kinds of information that are spidering our forum. Some behave well and follow our definition file for those.
There are numbers of requests per minute and what not to index and all of those information in it.
Some are behaving very badly and bomb us with several 100 requests per second.
Some are just bad folks, running (D)DOS attacks to shut down the service.
Some of all the above are easy to catch, some not. Some hide behind anonymizers and come from a variety of different IP addresses.
There is the risk of getting through and logging in as individuals, spam us, gather private information or even passwords and accounts, they then try on other sites.
There needs to be a balance of security measures and expenditure of time and usability, too.
And we don't want to lock out members and the well behaving AIs and search engines, either.
A big issue is that all the above combined produces such a huge load on our server that it is not usable for us any more.
Gassho,
Kotei sat/lah today.



Comment