linux-kernel - Re: NFS root + iptables in 2.6.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0809190057200.14395@hygvzn-guhyr.pnirva.bet>
Date:	Fri, 19 Sep 2008 01:00:43 -0700 (PDT)
From:	Richard A Nelson <cowboy@...ein.org>
To:	Wojciech Kromer <wojciech.kromer@....com.pl>
cc:	linux-kernel@...r.kernel.org
Subject: Re: NFS root + iptables in 2.6.25

On Fri, 19 Sep 2008, Wojciech Kromer wrote:

> # modprobe iptable_nat
> nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
> nfs: RPC call returned error 1
>
> Probably iptables changed it's default behavior from "allow all" to
> "deny all" at startup.
> Is there any way to change it back?
> I can't change anything after loading any iptable module, because all
> programs on filesystem are not accessible after loading...

NFS and iptables definitely takes some care - and there are still holes
- no way to specify ports for all requests...

but this seems odd...  you must've had some extant rules that suddenly
seemingly changed behaviour before the modprobe was done


-- 
Rick Nelson
[In 'Doctor' mode], I spent a good ten minutes telling Emacs what I
thought of it.  (The response was, 'Perhaps you could try to be less
abusive.')
 		-- Matt Welsh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/