zj1244
zj1244
因为之前使用masscan+nmap的扫描方式产生漏报太多了,所以后来琢磨单单使用nmap来扫的话,时间上是否能接受? 首先看看masscan+nmap扫描一个【c段(192.168.1.1-192.168.1.255)+1-65535端口】所用的时间,基本上在22分钟左右:  再看看使用以下参数扫描一个ip所用的时间大概在89秒左右: `nmap -sV 192.168.xxx.31 -p1-65535`   接着添加T4参数看看速度是否有变化:  可以看到也是89秒左右,接着继续添加--version-intensity 4参数:  可以看到速度缩短到43秒左右,但是带来的影响是有些指纹识别不出来,如下图:  这就需要分析哪些协议没识别出来,然后手动修改,首先在/usr/share/nmap/nmap-service-probes里查找rmiregistry,然后把rarity的值改成4就行了  但是有些指纹并没有rarity,如:jdwp  这时候可以通过`grep -r "Java Debug Wire Protocol" /usr/share/nmap/`查找rarity的判断在哪个文件,后来找到原来在/usr/share/nmap/scripts/jdwp-version.nse文件里,修改成4,这样就可以--version-intensity 4的时候也识别出来了 ...
在使用masscan做扫描的时候,经常会因为设置rate过大导致出现漏报,下图是扫同一台机器出现的完全不同的结果:  可以看出速率是70000的时候,一个端口都没扫到。而速率是7000的时候,扫到了两个端口。虽然之前就有预料到这个情况,但是还是没想到差距那么大,这也导致了扫描大量主机的时候,会有很多漏报,如下图:  之后应该不会使用masscan+nmap的方式来监控,原因就是漏报太多了
1. 查看当前系统安装了几个内核版本 ```bash rpm -qa|grep -i kernel-3.10 ```  2. 谷歌搜索并下载类似如下命名的三个文件: kernel-3.10.0-229.el7.x86_64.rpm kernel-tools-3.10.0-229.el7.x86_64.rpm kernel-tools-libs-3.10.0-229.el7.x86_64.rpm 3. 依次安装这三个文件: ```bash yum install kernel-tools-3.10.0-229.el7.x86_64.rpm ``` 如果安装失败就用rpm强制安装 ```bash rpm -ivh --force kernel-tools-3.10.0-229.el7.x86_64.rpm ``` 然后查看安装成功没有: ...
This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of...
This PR was automatically created by Snyk using the credentials of a real user. ### Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this...
This PR was automatically created by Snyk using the credentials of a real user. ### Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this...