Linux Netfilter discussions
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Rules in config file
Date: Wed, 10 Aug 2005 13:20:24 -0500	[thread overview]
Message-ID: <200508101320.24952.rob0@gmx.co.uk> (raw)
In-Reply-To: <20050810141804.e0876506@freedom.alpha-force.net>

On Wednesday 2005-August-10 07:18, Lists wrote:
> Would it be possible to somehow disable changing iptables rules from
> scripts and enable changing only from config file, which loading
> would be protected by special password defined in kernel? Or even

And what process is going to read that config file? A kernel driver? 
Sure, you can write kernel-space software to do things like this, but 
the reasoning behind it is not clear to me. I'd think the chances of 
inclusion in the mainstream kernel are close to zero.

> better, your could preset iptables rules in kernel. That rules would
> be unchangeable.

Is that good? BTW you can accomplish the same thing with an old 80386 
and /sbin/halt ... the machine keeps passing packets after the OS 
stops. I used to have a 386 firewall machine which died with a hard 
drive crash. I left it running 3-4 weeks thereafter, until I needed to 
make changes in the firewall rules.

> I think this would improve Linux firewall security on systems with
> complex and tight rules.

Complex rules often need care and attention. What is the threat model 
addressed by such a change? If someone hostile gets root on your 
machine, you're in trouble. Besides, I think SELinux presents a more 
comprehensive and well-considered approach to that possibility.
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


  reply	other threads:[~2005-08-10 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 12:18 Rules in config file Lists
2005-08-10 18:20 ` /dev/rob0 [this message]
2005-08-11  5:55 ` Jan Engelhardt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200508101320.24952.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --cc=netfilter@lists.netfilter.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox