Open bcoles opened 5 years ago
What would be a good solution or at least work-around to this? Giving the option to skip known hosting/cloud/protection providers, or when the AS peer list is above X, don't bother looking it up?
What would be a good solution or at least work-around to this?
I'd need to take a closer look at the functionality used to retrieve neighbors and BGP_AS_OWNER
. In the case of the latter, when I last read the code, it looked buggy, and unlikely to identify matches.
In the short term, a lookup_neighbors
Boolean module option to switch neighbor lookup off would be a good start. Currently, this module has no module options.
This module is among the longest runtime of all modules. I usually manually research data as its returned by Spiderfoot, especially for long running scans. It is frustrating to wait an eternity for BGP data, with no other data coming in, especially when the majority of the information retrieved by this module can be retrieved almost instantly with the sfp_bgpview
module.
Giving the option to skip known hosting/cloud/protection providers, or when the AS peer list is above X, don't bother looking it up?
I dislike the idea of blacklisting searching of specific providers. While Cloudflare is the most prominent example, I run into this issue frequently. Personally, I've found that the information identified is not worth the time it takes.
A huge amount of websites are protected by Cloudflare.
As a result, target domains resolve to Cloudflare IP addresses, with thousands of AS peers, which causes the
sfp_ripe
module to send thousands of queries to RIPE while attempting to lookup the AS owner (for nasn in neighs
).