M09Ic

Results 117 comments of M09Ic

I think this is a useful feature, before I encountered a similar requirement, I had to use python selenium to solve it

> 这个不完全是我说的办法, 因为如果存在泛解析, 现在subfinder和ksubdomain都会跳过这个域名, 但实际上泛解析不代表完全无用, 依旧有可能配置了几条有效的dns记录. 所以,我觉得就算是泛解析也要继续爆破, 只是可以将同ip的标记为无效解析记录, 只保留与随机子域名不同ip的dns记录

一加5t发现类似情况,所有手势失效 update: 安装完还能使用手势,重启后所有手势失效

https://github.com/projectdiscovery/mapcidr/pull/107/commits/53d4cf19f25c254cdee892156866c60db21d614a Resolved. test case1: > Some integration tests are failing and > Results tends to be cidr `mapcidr -cl ip.txt -fi 192.168.1.1,192.168.1.3 -silent` ip.txt: ``` 192.168.1.0/30 ``` output: ``` 192.168.1.0...

now, all integration tests pass, lol

> Hi, Just in case, you can do something like `export HOME='/tmp' && nuclei ...` to get around the fact that HOME is not defined, I use this technique and...

It should not be like that; the tags filter configured in config can only be effective for all targets. But if my input is like this: ``` 111.111.111.111:80 tags:gitlab 222.222.222.222:8080...

Same issue on Windows 11 as well.

当前的dubbo规则为: ``` - name: dubbo-remote focus: true default_port: - dubbo protocol: tcp rule: - regexps: vuln: - dubbo vuln: dubbo_unauthorized ``` 应该是返回值中出现了dubbo字段, 后续会改进该指纹

因为bash中#有特殊含义, 需要单引号包裹, `-w '/{$d#8}'`