As usual, remember it’ll be patched until heat death of the universe by 3rd parties that have this in their LTS distros, RHEL, Ubuntu, no clue about SUSE.
As a side note NetworkManager’s connection sharing uses unbound as the server.
Yes, but who will be looking for issues to patch? Particularly security bugs that only exhibit buggy behavior in the face of malicious input and are therefore unlikely to be discovered on accident by end users (and now that the project is unmaintained, developers).
Developers are not the ones looking for the issues to patch normally. The standard path starts from a security researcher who hopefully reports it to the project. The only difference is that they’ll have to report it to either some distro, or project zero, or something similar.
I’ve been using isc for a long time. I quite like my heirloom config but was just reading on what they suggest, Kea. They have a migration tool looks like. It emits JSON from your isc-dhcpd config. I’ll have to try this out.
As usual, remember it’ll be patched until heat death of the universe by 3rd parties that have this in their LTS distros, RHEL, Ubuntu, no clue about SUSE.
As a side note NetworkManager’s connection sharing uses unbound as the server.
Yes, but who will be looking for issues to patch? Particularly security bugs that only exhibit buggy behavior in the face of malicious input and are therefore unlikely to be discovered on accident by end users (and now that the project is unmaintained, developers).
Developers are not the ones looking for the issues to patch normally. The standard path starts from a security researcher who hopefully reports it to the project. The only difference is that they’ll have to report it to either some distro, or project zero, or something similar.
I think you mean dnsmasq.
Oooops, my bad. It is dnsmasq.
I’ve been using isc for a long time. I quite like my heirloom config but was just reading on what they suggest, Kea. They have a migration tool looks like. It emits JSON from your isc-dhcpd config. I’ll have to try this out.
We use kea at work at it’s mostly good. One of the good things is that you can store your configuration in database.
Another nice thing is it’s API. The configuration is just JSON, so it’s easy to deal with (like with Ansile) and so forth.