dedecms如何防止恶意会员注册和恶意文章发布 - 小灰博客

dedecms如何防止恶意会员注册和恶意文章发布

文章来源：小灰博客| 时间：2013-06-19 17:57:53| 作者：Leo　| 1 条评论

文章分类：IT技术分享、PHP 标签： dedecms

最近用dede整了个网站，需要开启会员注册和会员发布文章功能，蛋疼的是开启没几天里面恶意注册会员和未审核的恶意文章满屏都是，虽然不审核不会影响前台显示，但看着是闹心的很啊，接下来支几招防御措施，

1、在后台系统-系统设置-系统基本参数设置-会员设置里将会员使用权限开通状态设置为 -1 手动审核然后将动态和状态的审核开启了如图

2、然后在系统-系统设置-验证安全设置-验证问题设置里把注册和投稿都开启了，如图

3、接下来基本就防止住了恶意文章的发布，但你会发现后台有很多需要审核的恶意注册会员这时候需要在织梦模板文件下的member 目录下面的index.php，reg_new.php文件里面加个来路的判断语句，

1
2
3
4
5
6
7
8
9
10
11

<?php if( stristr ($_SERVER['HTTP_REFERER'],"我们的域名")) /*如果你网站是两个域名的话可以写成这样if( stristr ($_SERVER['HTTP_REFERER'],"我们的域名1")||stristr ($_SERVER['HTTP_REFERER'],"我们的域名2"))*/
{
原文件php代码的正文
}
else {
echo '<script>
alert("恶意用户自重！正常用户如出现此页面请联系管理员 - Leo QQ：512562970")
setTimeout("location.href=\'http://我们的域名\'",20)
</script>';
}
?>

这样基本就可以堵住恶意注册了！当不是本站域名下来的就会弹出上面的警告框！当然魔高一尺道高一丈，等被破解了后在想相应的办法！

如果该文章帮到了您，不妨帮忙分享支持下博主！
同时也欢迎各位技术爱好者加入IT技术群（点击即可）：70035098　互相交流学习！

分享该文章到：

一条评论

高阳说道：

2017 年 8 月 14 日上午 12:28

其实增加评论的难度，虽然有效堵住了恶意注册用户，也干掉了正常的热心用户！。。。。。。。真无语啊！！！ 😥

回复

发表回复取消回复

分类

Android (4)
ASP (4)
HTML (29)
IOS (8)
IT技术分享 (161)
Javascript (21)
MYSQL (12)
Photoshop (1)
PHP (71)
SEO (4)
Windows (17)
其他 (34)
安全技术 (19)
小技巧 (47)
小灰闲谈 (11)
心情随写 (10)
程序囧事 (44)

IT技术分享

最新评论

SECURITY UPDATE - Suspicious transfer of 1.5 BTC. Cancel? >> https://graph.org/COLLECT-BTC-07-23?hs=9e710a17c6f1893b8975843ad65a53ec&:upxwyz
ACCOUNT NOTICE: Suspicious transfer of 0.9 Bitcoin. Cancel? >> https://graph.org/COLLECT-BTC-07-23?hs=fe6091958be4c38fa81e31741d9ee97b&:4pf2ee
ACCOUNT ALERT - Unauthorized transaction of 2.0 Bitcoin. Block? >> https://graph.org/COLLECT-BTC-07-23?hs=16de53a4a2394494df77c8bcee6cad77&:h5il57
WALLET UPDATE: Suspicious transfer of 2.0 BTC. Stop? > https://graph.org/COLLECT-BTC-07-23?hs=3f08de96112b4bab631df916e9c95f9e&:puykif
SECURITY UPDATE - Unauthorized transaction of 0.9 BTC. Stop? > https://graph.org/COLLECT-BTC-07-23?hs=2ae440781044702fe525e5a4bc609633&:jeu7qm
+ 1.463083 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=9e710a17c6f1893b8975843ad65a53ec&:deoope
Notification; SENDING 1.340434 BTC. Assure => https://graph.org/Payout-from-Blockchaincom-06-26?hs=281dba697024abd3d1c5d7176ade2d86&:9no7ye
+ 1.741870 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=82b659c095cace05cbef312726b6e1d9&:ktokt2
+ 1.869464 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=d9564a149cf7ebbc725fcfce1bd3d512&:8u5u17
+ 1.520933 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=b3fb181a7a5a4b8271540fe16f846c4e&:77woi1
Ticket: Process 1.650130 BTC. Verify >> https://graph.org/Payout-from-Blockchaincom-06-26?hs=9e710a17c6f1893b8975843ad65a53ec&:0lc9pa
Email; + 1,927051 BTC. Go to withdrawal =>> https://graph.org/Payout-from-Blockchaincom-06-26?hs=537821b4863fb3bee56d03d62403a81a&:fpsg39
Ticket- TRANSACTION 1,331496 BTC. Assure => https://graph.org/Payout-from-Blockchaincom-06-26?hs=01da4417afbeba5c1c96ed80618a98be&:vv3cey
+ 1.156550 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=48af46897a78ce23e02d3d6d91453c82&:70ihvo
Email; TRANSACTION 1.839657 BTC. Receive => https://graph.org/Payout-from-Blockchaincom-06-26?hs=d9564a149cf7ebbc725fcfce1bd3d512&:aiwxke
+ 1.397578 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=389fe5cd6483dfc8b55bc3d3e1e86cfb&:uvq55v
+ 1.504191 BTC.GET - https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=9e710a17c6f1893b8975843ad65a53ec&:yumyj7
Message; Process 1.505974 BTC. GET => https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=00af77503aab4040b9414644cafc3051&:njhgiw
+ 1.732287 BTC.GET - https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=164145d501515772aa4824d0b8561afe&:vn4wwh
Message; Operation 1,932226 BTC. Assure =>> https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=82b659c095cace05cbef312726b6e1d9&:qwt1jk

链接表