From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Skylar Chang <chiaweic@codeaurora.org>
Cc: netfilter-devel@vger.kernel.org, npendhar@codeaurora.org
Subject: Re: [PATCH] libnfnetlink: Add API support for passing bound file descriptor
Date: Sun, 9 Apr 2017 00:21:13 +0200 [thread overview]
Message-ID: <20170408222113.GA9190@salvia> (raw)
In-Reply-To: <1491259467-21230-1-git-send-email-chiaweic@codeaurora.org>
On Mon, Apr 03, 2017 at 03:44:27PM -0700, Skylar Chang wrote:
> Add API support to accept pre-bound file descriptor from a
> privileged process for creating a handle. Also clean-up
> the handle without close the passing file descriptor. This
> paves the path for privilege separation.
I can take this patch... But as things are going, I would very much
push for libnfnetlink deprecation, so this API may be soon deprecated
which would be weird as it would be just something new...
It would be much better if you use libmnl for this. There's a new API
in libnetfilter_conntrack that mixes well with it.
Let me know.
prev parent reply other threads:[~2017-04-08 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 22:44 [PATCH] libnfnetlink: Add API support for passing bound file descriptor Skylar Chang
2017-04-08 22:21 ` Pablo Neira Ayuso [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=20170408222113.GA9190@salvia \
--to=pablo@netfilter.org \
--cc=chiaweic@codeaurora.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=npendhar@codeaurora.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).