cross-publish top X most abusive IPs to peer every Y seconds #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
peer can request threat intel peering (asks for specific rate, and type of abuse)
need to avoid sending data they already know about - either by literally tracking it or knowing intuitively (e.g. sending the same batch to everyone, or knowing they told us something)
configurable: firsthand or send data from trusted peers?
map(bad IP)->info, map(peer)->(told-ips) - empty struct (peer:ip->{})? (memory limitation, could use sqlite + caching)
if memory becomes a concern, btrees maybe? https://github.com/google/btree