On Thu, Mar 20, 2014 at 8:04 PM, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote:
martin.langhoff@xxxxxxxxx
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
--
martin.langhoff@xxxxxxxxx
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
On Thu, Mar 20, 2014 at 8:00 PM, Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote:
A firewall has mechanisms to filter for all domains, however onlycovering 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@xxxxxxxxx
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
martin.langhoff@xxxxxxxxx
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct