From: John Fastabend <john.r.fastabend@intel.com>
To: Chad Gray <chad938@hotmail.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Netfilter lacks ability to filter packets via Application-origin
Date: Wed, 19 Sep 2012 13:50:39 -0700 [thread overview]
Message-ID: <505A301F.5040201@intel.com> (raw)
In-Reply-To: <1348086252.2636.58.camel@bwh-desktop.uk.solarflarecom.com>
On 9/19/2012 1:24 PM, Ben Hutchings wrote:
> On Wed, 2012-09-19 at 15:40 -0400, Chad Gray wrote:
>> Users need the ability for Linux firewall to filter packets based on what
>> Application they are originating from. This ability is present in Mac and
>> Windows firewalls, but not Linux.
>>
>> For example, users would like ability to open Port 80 for Firefox, but keep
>> Port 80 closed for other applications.
>>
>> This ability enhances Privacy & Security of the user but also helps to better
>> inform the user about the comings and goings of internet traffic and what
>> application/s are causing the traffic.
>
> Most of the Linux Security Modules seem to support this sort of network
> policy.
>
> Ben.
>
Another approach might be to use the net_cls cgroups and set the
classid matching against it with tc or netfilters.
.John
next prev parent reply other threads:[~2012-09-19 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 19:40 Netfilter lacks ability to filter packets via Application-origin Chad Gray
2012-09-19 20:24 ` Ben Hutchings
2012-09-19 20:50 ` John Fastabend [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-21 16:39 Chad Gray
[not found] <COL002-W8067088C0C0B4682A10A0F39B0@phx.gbl>
2012-09-27 21:04 ` Chad Gray
2012-09-27 22:25 ` richard -rw- weinberger
2012-09-27 23:36 ` Ben Hutchings
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=505A301F.5040201@intel.com \
--to=john.r.fastabend@intel.com \
--cc=bhutchings@solarflare.com \
--cc=chad938@hotmail.com \
--cc=netdev@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).