From: Phil Oester <kernel@linuxace.com>
To: ZenSecurity <mailto@zensecurity.su>
Cc: netfilter@vger.kernel.org
Subject: Re: Bug in owner module
Date: Wed, 18 Dec 2013 13:15:02 -0800 [thread overview]
Message-ID: <20131218211501.GA21881@home> (raw)
In-Reply-To: <52ADE190.8010405@zensecurity.su>
On Sun, Dec 15, 2013 at 08:06:24PM +0300, ZenSecurity wrote:
> Kernel version: Linux lab 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64
> GNU/Linux
>
> # iptables -t nat -L
> DNAT tcp -- domain.com anywhere owner GID match
> usergroup to: X.X.X.X:80
>
> Rule:
> iptables -t nat -A OUTPUT -o eth0 -p tcp -s X.X.X.X -m owner --gid-owner
> usergroup -j DNAT --to-destination X.X.X.X:80;
>
> Doesn't match (usergroup exist).
Works fine here, on kernel.org kernel.
[root@f20_main ~]# uname -r
3.13.0-rc1+
[root@f20_main ~]# iptables -t nat -A OUTPUT -m owner --gid-owner 1000
[root@f20_main ~]# su - phil
[phil@f20_main ~]$ id
uid=1000(phil) gid=1000(phil) groups=1000(phil)
[phil@f20_main ~]$ ping -c1 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=1.02 ms
--- 10.10.10.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.022/1.022/1.022/0.000 ms
[phil@f20_main ~]$ logout
[root@f20_main ~]# iptables -t nat -nvL OUTPUT
Chain OUTPUT (policy ACCEPT 1 packets, 84 bytes)
pkts bytes target prot opt in out source destination
1 84 all -- * * 0.0.0.0/0 0.0.0.0/0 owner GID match 1000
I suggest filing a bug with Debian bugzilla if you suspect a problem in a Debian
kernel.
Phil
prev parent reply other threads:[~2013-12-18 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 13:57 Bug in owner module ZenSecurity
2013-12-15 16:38 ` Phil Oester
[not found] ` <52ADE190.8010405@zensecurity.su>
2013-12-18 21:15 ` Phil Oester [this message]
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=20131218211501.GA21881@home \
--to=kernel@linuxace.com \
--cc=mailto@zensecurity.su \
--cc=netfilter@vger.kernel.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