3rd party forum, gallery, blog open sources systems are the targets of these hacker software. The hacker software auto register and then post the porn, gambling etc. info.
In addition to keep these open source system updates with the most current versions or security updates, in addition to use all these built in features such as "virtual confirmation", email address required to activate the account etc.
What else we can do? Basically, I have been doing these and still not good enough to fence off the attacks.
I am thinking, due to these software are usually written to attack these open source systems. If in the registeration process, in addition to the system built in "virtual confirmation", email required to activate account feautures.
If I add some of my own codes as the additioanl confirmation information. Such as add another line of confirmation code (my own codes), this added custom design confirmation field will fence off most hack software specially designed to attack that certain open source system, right?
What is your solution in fencing off these attacks on open source forum, gallery and blog systems?