From: Cedric Blancher <blancher@cartel-securite.fr>
To: Gustav Svensson <gurra16@spray.se>
Cc: netfilter@lists.netfilter.org
Subject: Re: Control outbound access on a per-application level
Date: 02 Oct 2002 17:38:33 +0200 [thread overview]
Message-ID: <1033573113.735.45.camel@elendil> (raw)
In-Reply-To: <1033569217024171@spray.se>
Le mer 02/10/2002 à 17:23, Gustav Svensson a écrit :
> Is it possible to set "outbound" rules based on what binary application it is that
> wants to access the Internet?
You can use --cmd-owner switch from owner module (lastest patch-o-matic)
which provides you the ability to choose a command name.
But unfortunately, it just match the command name, and does not check
binaries location in the filesystem. If I authorize ping command, anyone
who launch a command called ping will be granted (e.g. ln -s
/usr/bin/ssh ping), whatever it is. Which means it is imho quite
uneffective on systems where users can build and/or install their own
stuff, even if you considerer hardening command filtering with other
stuff :
iptables -A OUTPUT -m owner --cmd-owner ping -p icmp \
--icmp-type echo-request -j ACCEPT
I am still to launch to tool that communicate over ICMP, as an example.
I was considering a device/inode check, but I am afraid it is far over
my skills to add this to that very module. You would give iptables the
complete path and tool will get device ID and inode number for the
binary and store it as match. Then, Netfilter checks the file that owns
the socket, check it device ID and inode number and take the decision.
My 2 cents of euro.
--
Cédric Blancher
Consultant en sécurité des systèmes et réseaux - Cartel Sécurité
Tél: +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
PGP KeyID:157E98EE FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
next prev parent reply other threads:[~2002-10-02 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 15:46 Control outbound access on a per-application level Gustav Svensson
2002-10-02 15:38 ` Cedric Blancher [this message]
2002-10-02 18:51 ` Mitesh P Choksi
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=1033573113.735.45.camel@elendil \
--to=blancher@cartel-securite.fr \
--cc=gurra16@spray.se \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.