From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 32465@debbugs.gnu.org
Subject: [bug#32465] Add iptables service
Date: Mon, 10 Sep 2018 14:51:58 +0200 [thread overview]
Message-ID: <87y3c9frbl.fsf@gnu.org> (raw)
In-Reply-To: <cu7zhww2sfr.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 05 Sep 2018 15:10:24 +0530")
Hello,
Arun Isaac <arunisaac@systemreboot.net> skribis:
>> it's not directly an answer to arun's patch (it is great), but I
>> recently came accross firemason
>> (http://www.cs.yale.edu/homes/zhai-ennan/firemason.pdf and
>> https://github.com/BillHallahan/FireMason) and I thought we could
>> implement something similar.
>
> This sounds interesting. I'll read about it, and if I can, try to
> implement something similar for Guix.
Agreed, it looks nice.
>> Of course, we should provide a mechanism to load files as a fallback, in
>> which case additional rules from services should be ignored.
>
> Yes, I think this iptables service should exist independently as a
> fallback. So, I'll finish and push these services before studying
> firemason.
The nice thing is that we could detect conflicting iptables rules
statically if we wanted to: ‘guix system reconfigure’ would proceed if
and only if there are no conflicting rules. I don’t know how difficult
and how annoying that could be, but it might be worth considering (as
future work…).
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-09-10 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 11:24 [bug#32465] Add iptables service Arun Isaac
2018-09-04 13:14 ` Ludovic Courtès
2018-09-04 13:52 ` Julien Lepiller
2018-09-05 9:40 ` Arun Isaac
2018-09-10 12:51 ` Ludovic Courtès [this message]
2018-09-05 9:42 ` Arun Isaac
2018-09-14 10:59 ` Arun Isaac
2018-09-17 21:05 ` Ludovic Courtès
2018-09-18 6:24 ` Arun Isaac
2018-09-18 14:39 ` Ludovic Courtès
2018-09-18 16:02 ` Arun Isaac
2018-09-19 20:41 ` Ludovic Courtès
2018-09-20 7:50 ` bug#32465: " Arun Isaac
2018-09-11 6:53 ` [bug#32465] " Björn Höfling
2018-09-11 8:43 ` Arun Isaac
2018-09-15 12:27 ` Rutger Helling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3c9frbl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32465@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).