From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Eric Paris <eparis@parisplace.org>,
netfilter@vger.kernel.org, sds@tycho.nsa.gov
Subject: Re: decipher the secmark number from nf_conntrack/ip_conntrack
Date: Fri, 24 Sep 2010 01:27:10 +0100 [thread overview]
Message-ID: <4C9BF05E.5070106@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1009240126360.28190@obet.zrqbmnf.qr>
> In a way, it did display the secmark. :-)
Of course it doesn't. This is a number generated internally by the sel
engine (it is called sid). End users were never meant to see this number
- at all. selctx is the field which is designed for user space and for
'general' consumption.
> Just like ipt_LOG prints
> nfmark or IP addresses. The values may not mean much to the outside
> world, but that's what we have DNS and selctx (James's original
> naming) for.
>
Again, all of the above is meant to be in userspace, sid isn't.
> If users would not
> constantly insist on using outdated interfaces (and I _do_ grant
> things their transition time),
Who are you to judge what consumers - both users and developers alike -
should or shouldn't use?
> and if maintainers would not always
> give in to these users, we would have less code to worry about, or
> even have these discussions.
>
Yeah right, so if I need to see a secmark on a particular connection
instead of typing a simple 'cat /proc/net/nf_conntrack', or, as is in my
case use an existing tool (Shorewall) to check for such contexts, lets
just bloat my system with yet another set of useless tools, install
conntrack-utils and execute 'conntrack -L' for that privilege instead?!
You should be working for Microsoft!
I am not, for a moment, suggesting that netfilter tools should not be
able to map and get the context - what I am saying is that consumers
(both users and developers) should be given a choice to use both methods
- either via /proc (as is the case right now) as well as by other 3rd
party userspace tools - the choice is theirs to make.
next prev parent reply other threads:[~2010-09-24 0:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 23:04 decipher the secmark number from nf_conntrack/ip_conntrack Mr Dash Four
2010-09-20 0:48 ` Jan Engelhardt
2010-09-20 10:41 ` Mr Dash Four
2010-09-20 12:23 ` Jan Engelhardt
2010-09-20 12:42 ` Mr Dash Four
2010-09-20 18:15 ` Mr Dash Four
2010-09-20 21:49 ` Tom Eastep
2010-09-20 23:26 ` Jan Engelhardt
2010-09-20 23:55 ` Tom Eastep
2010-09-21 9:59 ` Mr Dash Four
2010-09-21 20:13 ` Mr Dash Four
2010-09-21 20:26 ` Eric Paris
2010-09-21 21:00 ` Eric Paris
2010-09-21 22:38 ` Mr Dash Four
2010-09-21 22:42 ` Jan Engelhardt
2010-09-21 22:51 ` Mr Dash Four
2010-09-21 23:10 ` Eric Paris
2010-09-21 23:35 ` Jan Engelhardt
2010-09-23 18:39 ` Eric Paris
2010-09-23 18:49 ` Jan Engelhardt
2010-09-23 18:52 ` Eric Paris
2010-09-23 18:57 ` Jan Engelhardt
2010-09-23 18:58 ` Eric Paris
2010-09-23 19:20 ` Mr Dash Four
2010-09-23 19:51 ` Jan Engelhardt
2010-09-23 20:05 ` Mr Dash Four
2010-09-23 20:18 ` Mr Dash Four
2010-09-23 20:34 ` Eric Paris
2010-09-23 20:38 ` Mr Dash Four
2010-09-23 20:53 ` Jan Engelhardt
2010-09-23 20:56 ` Mr Dash Four
2010-09-23 21:23 ` Jan Engelhardt
2010-09-23 21:38 ` Mr Dash Four
2010-09-23 22:12 ` Jan Engelhardt
2010-09-23 22:30 ` Mr Dash Four
2010-09-23 22:42 ` Eric Paris
2010-09-23 23:59 ` Jan Engelhardt
2010-09-24 0:24 ` Tom Eastep
2010-09-24 0:32 ` Mr Dash Four
2010-09-24 1:18 ` Jan Engelhardt
2010-09-24 0:27 ` Mr Dash Four [this message]
2010-09-23 20:42 ` Jan Engelhardt
2010-09-23 20:53 ` Mr Dash Four
2010-09-21 22:29 ` Mr Dash Four
2010-09-22 2:25 ` Tom Eastep
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=4C9BF05E.5070106@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=eparis@parisplace.org \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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