On Thu, Mar 20, 2014 at 8:04 PM, Martin Langhoff <martin.langhoff@gmail.com> wrote:
On Thu, Mar 20, 2014 at 8:00 PM, Lennart Poettering <mzerqung@0pointer.de> wrote:
A firewall has mechanisms to filter for all domains, however only
covering a smaller number of generic, low-level matches and actions.

From a usability PoV, /etc/hosts.{allow,deny} is good. I wonder if teaching firewalld to support some of that functionality would help here.

To clarify: what I mean is that firewalld could parse the legacy files, interpreting the rules that are translatable, failing safely for those that are are not.

cheers,



m
--
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff



--
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff