From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH 3/3] xt_owner match
Date: Mon, 19 Nov 2007 18:10:24 +0100 [thread overview]
Message-ID: <4741C380.1090409@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711191751580.32378@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Nov 19 2007 16:43, Patrick McHardy wrote:
>
>>> + filp = skb->sk->sk_socket->file;
>>> + if (filp == NULL)
>>> + return false;
>> What would be nice is to allow matching whether a socket exists,
>> without UID/GID. I had a patch for this for a long time, but
>> lost it somewhere.
>
> Do you mean xt_socket from TPROXY?
Well, xt_socket does a lookup. What my patch did was allow matching
on the existance of a socket related to that packet (simply:
iptables ... -m owner -j .... Your patch actually already allows that,
but doesn't allow inversion for this. But now that you mention it,
I did use it for incoming packets combined with a socket lookup,
its probably not that useful for outgoing packets. It would only
require a single new flag to properly support this though.
next prev parent reply other threads:[~2007-11-19 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 13:00 [PATCH 1/3] xt_tos match Jan Engelhardt
2007-11-16 13:00 ` [PATCH 2/3] xt_TOS target Jan Engelhardt
2007-11-19 10:40 ` Patrick McHardy
2007-11-19 11:46 ` Jan Engelhardt
2007-11-16 13:01 ` [PATCH 3/3] xt_owner match Jan Engelhardt
2007-11-19 15:43 ` Patrick McHardy
2007-11-19 16:56 ` Jan Engelhardt
2007-11-19 17:08 ` Jan Engelhardt
2007-11-19 17:12 ` Jan Engelhardt
2007-11-19 17:18 ` Patrick McHardy
2007-11-19 17:10 ` Patrick McHardy [this message]
2007-11-19 10:37 ` [PATCH 1/3] xt_tos match Patrick McHardy
2007-11-19 11:39 ` 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=4741C380.1090409@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).