Recently, some of our Z-BLOGGERs are thinking of making a plug-in to stop SPAM. Of course, the solution is not to be without it. It is just to build a super strong server, but unfortunately I can't afford it. Then... we had to think from the perspective of SPAMMER.
Those who understand it may know that the basic principle of SPAM software is [Search target] - Enter the website - Scan the verification code - OCR - [Fill in the form] - POST. We can prevent every step, and the more realistic thing is to prevent the SPAM software from successfully OCRing and issuing verification codes. The verification code that comes with Z-BLOG is really weak, and the interference point is equal to none. I feel that the numbers in the verification code can be easily analyzed. The solution is to change the verification code program.
This verification code program (which I am using now) was dug out from the Moonlight message book and slightly modified to adapt to Z-BLOG. I personally think it is a bit difficult to compile the verification code of the software OCR, and it should be exchanged for a moment of peace. Of course, this is just a temporary measure. If it is widely used, there will inevitably be experts to crack it. So... it's best to have a server on the official side. Sometimes, I think it's good to commercialize or introduce investment properly~
The results are still being tested, starting from 3-28 nights. So far (07-03-30), a total of 1 SPAM (including intercepted ones). The content is different from other SPAMs. It should not be the work of the spam SEO website (with bold additions of 2 links), and it is not the submission of "Google added a web malware detection" searched in a general search engine? 》, but in my message book. According to the result of REFERER, it should be from the home page (it is not ruled out that you go in from another place without executing the script or submitting the refer information), and it is suspected that it is manual SPAM (UPDATE: Haphic also received the same one. Is it manual? The verification code he used is the original...), and the effect of changing the verification code needs to be observed...
c_validcode.asp code
The code copy is as follows:
<%@CODEPAGE=65001%>
<%OptionExplicit%>
<%
'OnErrorResumeNext
%>
<!--#includefile="../c_option.asp"-->
<!--#includefile="../function/c_function.asp"-->
<%
Response.buffer=true
CallCom_CreatValidCode("CheckCode")
Rem generates verification code picture
SubCom_CreatValidCode(pSN)
ConstcodeLenMin=5'Verification code digit range
ConstcodeLenMax=5'Verification code digit range
ConstcOdds=2'The probability of miscellaneous spots appearing
ConstdbtTimes=1' Number of interferences