From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Beluc <beluc.mailing@free.fr>, netfilter@vger.kernel.org
Subject: Re: problem getting uid in nfqueue
Date: Tue, 22 Jun 2010 10:18:20 +0200 [thread overview]
Message-ID: <4C2071CC.60300@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1006221003230.13935@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Monday 2010-06-21 22:51, Beluc wrote:
>
>
>> no idea ? maybe i didn't explain very well :/
>>
>> i saw that when using LOG target in OUTPUT policy, there is the user's uid who
>> send packet.
>>
>
> That is not the user's uid, but the uid of the socket's creator.
Filtering based on UID is best done using the owner match. nfnetlink_queue
currently doesn't supply the UID/GID, but it could be added easily.
next prev parent reply other threads:[~2010-06-22 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:37 problem getting uid in nfqueue beluc.mailing
2010-06-21 20:51 ` Beluc
2010-06-22 8:03 ` Jan Engelhardt
2010-06-22 8:18 ` Patrick McHardy [this message]
2010-06-22 8:45 ` Jan Engelhardt
2010-06-22 8:49 ` Patrick McHardy
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=4C2071CC.60300@trash.net \
--to=kaber@trash.net \
--cc=beluc.mailing@free.fr \
--cc=jengelh@medozas.de \
--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