小灰博客--小灰IT技术博客 | sky00.com

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 互相交流学习!

分享该文章到:

一条评论

  1. 高阳说道:

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



发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

分类

最新评论

  • + 1.137921 BTC.NEXT - https://yandex.com/poll/DCTzwgNQnzCykVhgbhD581?hs=32fb9425b62f8025c93b1a741cda529c&:didcyq
  • + 1.779120 BTC.GET - https://yandex.com/poll/76RuKke5vYn6W1hp2wxzvb?hs=46cca2220f62b645c465c3659609f169&:4jnm98
  • Ticket: + 1,450330 BTC. Get > https://yandex.com/poll/76RuKke5vYn6W1hp2wxzvb?hs=d2e9f25426f06f324d26af9866fa1537&:girqat
  • + 1.962123 BTC.NEXT - https://yandex.com/poll/5JjqQt7R61CTYdYVd17t6p?hs=55473f62ca80b75d789e64fa58e49760&:7818gc
  • + 1.474092 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=9e710a17c6f1893b8975843ad65a53ec&:3dvnw2
  • + 1.478940 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=111a7c8b116abe352c74949c481b3c7f&:c7t0pv
  • + 1.414945 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=189b84788c5e6405c53f7dd1193b9874&:umgly6
  • + 1.689074 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=c5d93ba1cba130eac0442e0b01e08d9d&:iy7mdu
  • Notification: TRANSACTION 1.129243 BTC. Continue >> https://graph.org/Ticket--58146-05-02?hs=82b659c095cace05cbef312726b6e1d9&:fzvug0
  • + 1.463044 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=f4f7ece997f382758bf7917d8d281a38&:swrwfu
  • + 1.949656 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=d9564a149cf7ebbc725fcfce1bd3d512&:0si3ke
  • + 1.6825 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=e8e513973712a3c92cfc5061bded6465&:jq3tz4
  • + 1.674227 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=9e710a17c6f1893b8975843ad65a53ec&:5q176p
  • Ticket- Process 1,851260 BTC. Receive >> https://graph.org/Official-donates-from-Binance-04-01?hs=81d107938621831ce06bfc98e59470ae&:xtjbtk
  • + 1.419261 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=558cdf18520cfb0ab9368563ad878fe3&:t1ixi5
  • + 1.200600 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=20bcd57ec809274e19061c909e168662&:2ixvv9
  • + 1.681136 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=48af46897a78ce23e02d3d6d91453c82&:xg3n0k
  • Message: Operation 1,579770 bitcoin. Withdraw => https://graph.org/Official-donates-from-Binance-04-01?hs=8b618b6f3e2558ea545b01f25c66ea45&:f5w4y0
  • Reminder- TRANSFER 1.299580 BTC. Get => https://graph.org/Official-donates-from-Binance-04-01?hs=a0af85c70258e2d35864223f8bf1561e&:bapbbx
  • + 1.195608 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=9e710a17c6f1893b8975843ad65a53ec&:102182