The idea about a different approach to block bad guys...
Hi guys... this channel is for a slow burning idea, very unfinished but yet bubbling under the surface.... what we all tries to accomplish is making some DNS or lists records that can and will help protect against various things.
But what we are doing now is kind of upside down... we are imported a lot of outdated material, spending a lot of hours - days - month to clean this up, and yet we are always behind the workflow.
The idea is:
The idea is that we have the central DB which stores all the BadWare, now every user would be able to:
- Users upload there own list (records, ie. we uses RPZ (Response Policy Zones) have them availability tested for (on- offline) state
- User driven categorizing and classify (severity) any known records.
- Have an multi export tool to many formats: various DNS and RPZ format, CSV, Hosts etc.
- There will not be any hosted whitelisting for extraction, at least to begin with. (resources)
Now, when you extract the data from the DB by category/severity you'll need you personal whitelist, as it always should be, to exclude any known records from the extracted list.
This means you in the future would have many more users contributing to one central place, rather than as today, where there are 1000's of lists containing mostly the same records.
It does also means that users would need to be rethinking from blacklisting to whitelisting 😃 😉
Any record in the DB will, at least in the startup, be referring to a issue on mypdns.org for the log(Why) of classification.
We will build-in both a web interface for manual contribution of new records + there will of curse be an API
Any suggestions are more than welcome, and we will be looking forward to a good future teamwork.