近期查看个人Vps的Mysql日志出现:MySQL – no reverse address mapping,外网看来很不安全。
在我的个人VPS上发现如下SQL:
查了下Google发现是有人想从外网登录Mysql,做了下尝试给Mysql拒绝了,老外解释如下:
“[Warning] IP address ‘XXX.XXX.XXX.XX’ could not be resolved: no reverse address mapping.”
The reverse address mapping is basically requesting from the DNS, “I have this IP address can you give me a domain name associated with this IP address”. The domain name is needed in the login verification i.e. authentication is based on username and host. The host in this case is not an IP address but a host name.
So for example, if the authentication in the server is myuser@localhost, we need to verify that the person is logged on from localhost.
The person logging in will have an identified IP address but not a domain name, so we need to convert the IP address to a domain name. The domain name is then compared along with the username to verify which entry in the mysql.user table should be used to complete verification.
不光是Mysql,连ssh都有人尝试登录:
外网很不安全哇,大家小心为好。
查了下Google发现是有人想从外网登录Mysql,做了下尝试给Mysql拒绝了,老外解释如下:
“[Warning] IP address ‘XXX.XXX.XXX.XX’ could not be resolved: no reverse address mapping.”
The reverse address mapping is basically requesting from the DNS, “I have this IP address can you give me a domain name associated with this IP address”. The domain name is needed in the login verification i.e. authentication is based on username and host. The host in this case is not an IP address but a host name.
So for example, if the authentication in the server is myuser@localhost, we need to verify that the person is logged on from localhost.
The person logging in will have an identified IP address but not a domain name, so we need to convert the IP address to a domain name. The domain name is then compared along with the username to verify which entry in the mysql.user table should be used to complete verification.
不光是Mysql,连ssh都有人尝试登录:
外网很不安全哇,大家小心为好。
作者:jackxiang@向东博客 专注WEB应用 构架之美 --- 构架之美,在于尽态极妍 | 应用之美,在于药到病除
地址:https://jackxiang.com/post/4783/
版权所有。转载时必须以链接形式注明作者和原始出处及本声明!
评论列表