> This looks like a neat project and it is great that you've open sourced it. I > can see how it would be useful for folks that want an open source solution to > deploy their own honeypots and feed that back into private blocklists.
Thanks Rob. > On a wider, shared blocklist level, this seems like a relatively simple > problem to solve, but the parallels with email spam are hard to avoid. I know. Especially the p2p part. > There have been a few similar blocklists including the ITSPA/Comms Council > Cargill & Cox DNS based project whose name temporarily escapes my braincells, > and the apiban project (Fred Posner - Kamailio, LOD) which seems to be > gaining some traction. snitch, but that is a passive pcap tool. I wanted batteries included. yep, I like APIBAN, but all the data sits there. It is free and centralised. Clients are open source. No phone numbers. > I guess the feature of your project is the open federation protocol, but I > think there are reasons that most approaches to this kind of filtering are > behind a curtain controlled by gatekeeper and Matthew covered most of them. > There is a very high trust bar for most providers to import filtering > decisions into their network, and I can't think of any non-curated approach > that has ever flown. > There are much smarter people than me that will have solved this I'm sure. I think it's the "rules based" approach, vs ML approach etc. I just want to get the data in folks hands and I think the filtering part will solve itself. > It will be interesting to see how this pans out though, certainly looks like > a great learning and data collection project. That's why I've started it. I've already learned a ton! Packaging it for one!
