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 1/2] [NETFILTER]: xt_socket: rename from xt_owner
Date: Thu, 24 Jan 2008 08:54:56 +0100 [thread overview]
Message-ID: <47984450.7070309@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801220022580.25080@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> commit 7ed2d25d54b696074c8e787a03a1513d245e8caa
> Author: Jan Engelhardt <jengelh@computergmbh.de>
> Date: Mon Jan 21 13:34:48 2008 +0100
>
> [NETFILTER]: xt_socket: rename from xt_owner
>
> xt_owner matches against the ownership of a socket. Currently this
> only work in the output path when skb->sk is set. I recalled tproxy's
> xt_socket, which does an explicit socket for the input path and
> thought that this could be useful for xt_owner. Both modules would
> then do a lookup, so let's just combine the code into one module.
>
> This patch renames xt_owner to xt_socket; the tproxy bits and input
> path socket lookup will be added when tproxy gets merged.
This seems unnecessary. We can consider the rename once tproxy
gets merged, but things are progressing very slowly.
next prev parent reply other threads:[~2008-01-24 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 23:23 [PATCH 1/2] [NETFILTER]: xt_socket: rename from xt_owner Jan Engelhardt
2008-01-21 23:23 ` [PATCH 2/2] [NETFILTER]: xt_socket: allow matching UID/GID ranges Jan Engelhardt
2008-01-24 7:55 ` Patrick McHardy
2008-01-24 7:54 ` Patrick McHardy [this message]
2008-01-24 11:31 ` [PATCH 1/2] [NETFILTER]: xt_socket: rename from xt_owner 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=47984450.7070309@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).