From: "Tvrtko A. Ursulin" <tvrtko.ursulin@sophos.com>
To: linux-kernel@vger.kernel.org
Subject: Out of tree module using LSM
Date: Wed, 28 Nov 2007 12:42:52 +0000 [thread overview]
Message-ID: <200711281242.52941.tvrtko.ursulin@sophos.com> (raw)
Hi Linus, all,
During one recent LKML discussion
(http://marc.info/?l=linux-kernel&m=119267398722085&w=2) about LSM going
static you called for LSM users to speak up.
We here at Sophos (the fourth largest endpoint security vendor in the world)
have such a module called Talpa which is a part of our main endpoint security
product for Linux that protects from viruses and malware hosted on Linux,
including those targetting Windows or other connected devices,
(http://www.sophos.com/products/enterprise/endpoint/security-and-control/linux/index.html)
which is GPL code and has been in the field for almost three years now. It's
source code has been shipping with the product from the start. We also have
a SourceForge project at http://sourceforge.net/projects/talpa/ to host it.
In essence, what our module does is it intercepts file accesses and allows
userspace daemons to vet them. One of the means we implemented that is
through LSM and although it is not a perfect match for such use we prefer to
use an official interface. Unfortunately, with time it became impossible to
use LSM on some distributions (SELinux) so we had to implement other
intercept methods which are significantly less nice, and which may also
become unworkable over time.
The main point here is that making LSM not available for modules makes our
life even more difficult and we would like to ask you to revert that change
until another acceptable, secure solution is found.
At this point I would not like this to turn into a discussion on technical or
code merits of our current approach. It is just that usage scenarios of
(dis-)allowing access to files based on their content, regardless of the
actual details, do sound like a reasonable idea. What we would like to do is
to start discussion about possible solutions in which other interested
parties will hopefully join and in future create some progress on this front.
--
Tvrtko August Ursulin
Senior Software Engineer, Sophos
Tel: 01235 559933
Web: www.sophos.com
Protecting business against viruses, spyware, spam and policy abuse
Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon,
OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
next reply other threads:[~2007-11-28 12:45 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 12:42 Tvrtko A. Ursulin [this message]
2007-11-28 14:41 ` Out of tree module using LSM Christoph Hellwig
2007-11-28 16:38 ` Casey Schaufler
2007-11-28 16:46 ` Christoph Hellwig
2007-11-28 17:39 ` Stephen Hemminger
2007-11-28 18:22 ` tvrtko.ursulin
2007-11-28 19:50 ` Alan Cox
2007-11-29 16:12 ` tvrtko.ursulin
2007-11-29 0:12 ` James Morris
2007-11-29 16:27 ` Jon Masters
2007-11-29 16:51 ` Greg KH
2007-11-29 16:51 ` Stephen Hemminger
2007-11-29 16:52 ` Jan Engelhardt
2007-11-29 0:51 ` Jan Engelhardt
2007-11-29 1:45 ` Casey Schaufler
2007-11-28 18:15 ` Valdis.Kletnieks
2007-11-28 18:30 ` Al Viro
2007-11-29 0:38 ` Greg KH
2007-11-29 0:53 ` Jan Engelhardt
2007-11-29 1:07 ` Greg KH
2007-11-29 16:36 ` Jon Masters
2007-11-29 16:47 ` Greg KH
2007-11-29 16:53 ` Jan Engelhardt
2007-11-29 16:57 ` Christoph Hellwig
2007-11-29 17:27 ` Alan Cox
2007-11-29 22:58 ` Andi Kleen
2007-12-08 10:50 ` Pavel Machek
2007-11-29 17:03 ` Greg KH
2007-11-29 17:35 ` Ray Lee
2007-11-29 17:45 ` Greg KH
2007-11-29 18:03 ` Ray Lee
2007-11-29 18:19 ` Justin Banks
2007-11-29 18:38 ` Jon Masters
2007-11-29 17:51 ` Al Viro
2007-11-29 17:05 ` Jon Masters
2007-11-29 17:14 ` Greg KH
2007-11-29 16:26 ` tvrtko.ursulin
2007-11-29 17:36 ` Alan Cox
2007-11-29 18:40 ` Ray Lee
2007-11-29 18:56 ` Jon Masters
2007-11-29 19:11 ` Ray Lee
2007-11-29 19:45 ` Jon Masters
2007-11-29 20:56 ` Valdis.Kletnieks
2007-11-29 22:08 ` Al Viro
2007-11-30 0:50 ` James Morris
2007-11-29 23:31 ` Jon Masters
2007-11-29 21:45 ` Alan Cox
2007-11-29 22:12 ` Justin Banks
2007-11-30 1:48 ` Al Viro
2007-11-30 15:37 ` Justin Banks
2007-11-29 23:34 ` Jon Masters
2007-11-30 6:20 ` Valdis.Kletnieks
2007-11-30 13:30 ` Alan Cox
2007-11-29 21:09 ` Andi Kleen
2007-11-28 19:20 ` Andi Kleen
2007-11-28 19:52 ` Alan Cox
2007-11-28 20:05 ` Valdis.Kletnieks
2007-11-29 16:39 ` tvrtko.ursulin
2007-12-01 8:43 ` Pavel Machek
2007-12-02 19:44 ` Valdis.Kletnieks
2007-12-02 20:02 ` Arjan van de Ven
2007-12-02 20:06 ` Andi Kleen
2007-12-02 20:22 ` Pavel Machek
2007-12-02 21:09 ` Valdis.Kletnieks
2007-12-02 21:56 ` Pavel Machek
2007-12-02 23:15 ` Jan Engelhardt
2007-12-02 23:23 ` Pavel Machek
2007-11-29 0:58 ` Greg KH
2007-11-30 20:52 Crispin Cowan
2007-11-30 21:36 ` James Morris
2007-11-30 23:52 ` Crispin Cowan
2007-12-01 0:05 ` James Morris
[not found] <9uzZr-6iz-19@gated-at.bofh.it>
[not found] ` <9uUrm-5w3-27@gated-at.bofh.it>
[not found] ` <9uVGz-7uQ-19@gated-at.bofh.it>
[not found] ` <9uWCC-xI-13@gated-at.bofh.it>
[not found] ` <9uWMp-Ix-13@gated-at.bofh.it>
[not found] ` <9uX5A-1rs-1@gated-at.bofh.it>
[not found] ` <9uXyK-24f-23@gated-at.bofh.it>
2007-12-03 22:45 ` Bodo Eggert
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=200711281242.52941.tvrtko.ursulin@sophos.com \
--to=tvrtko.ursulin@sophos.com \
--cc=linux-kernel@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).