From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: netfilter-devel@vger.kernel.org, abirvalg@lavabit.com
Subject: Re: nfqueue library setup requires root
Date: Thu, 2 Feb 2012 19:49:05 +0100 [thread overview]
Message-ID: <20120202184905.GB5268@1984> (raw)
In-Reply-To: <4F29679F.6090704@mutluit.com>
On Wed, Feb 01, 2012 at 05:26:07PM +0100, U.Mutlu wrote:
> abirvalg@lavabit.com wrote, On 12/29/11 15:00:
> >Hi,
> >I launched my application with CAP_NET_ADMIN capability, yet both nfq_unbind_pf and nfq_bind_pf produce an error.
> >When I setuid(0) no error is produced and everything works as expected.
> >Could you please confirm that Library setup operations require root.
> >Isn't it a bit misleading that libnetfilter_queue docu states that CAP_NET_ADMIN is required without mentioning root permissions.
> >Would it be possible to do Library Setup with only CAP_NET_ADMIN and without root priviliges in future versions?
>
> On a host node I didn't need CAP_NET_ADMIN when starting it as root
> (ie. maybe on my system root already has that cap by default; would make sense).
Yes, root is fine. You should also get it running with CAP_NET_ADMIN.
> But on a VPS on the same host node I couldn't get it working yet.
> It always gives errno=111 (ECONNREFUSED; "Connection refused").
This has nothing to do with permissions (in that case you'll hit
-EPERM).
> Does yours work in a virtual machine, ie. on a VPS ?
By "virtual machine" you mean one linux container (lxc)?
next prev parent reply other threads:[~2012-02-02 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:00 nfqueue library setup requires root abirvalg
2012-02-01 16:26 ` U.Mutlu
2012-02-02 18:49 ` Pablo Neira Ayuso [this message]
2012-02-02 21:52 ` U.Mutlu
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=20120202184905.GB5268@1984 \
--to=pablo@netfilter.org \
--cc=abirvalg@lavabit.com \
--cc=for-gmane@mutluit.com \
--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).