From: Arjan van de Ven <arjan@infradead.org>
To: "Makan Pourzandi (QB/EMC)" <makan.pourzandi@ericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Serue Hallyen <serue@us.ibm.com>,
Axelle Apvrille <axelle_apvrille@rc1.vip.ukl.yahoo.com>,
disec-devel@lists.sourceforge.net
Subject: RE: [ANNOUNCE] Release Digsig 1.5: kernel module for run-timeauthentication of binaries
Date: Mon, 24 Apr 2006 18:47:57 +0200 [thread overview]
Message-ID: <1145897277.3116.44.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA29D361@ecamlmw720.eamcs.ericsson.se>
On Mon, 2006-04-24 at 12:27 -0400, Makan Pourzandi (QB/EMC) wrote:
> Hi Arjan,
>
> I hope I correctly understood your question, DigSig uses LSM hooks to
> check the digital signature before loading it, then as long as your elf
> loader uses kernel system calls, it's covered by DigSig.
ok I have to admit that this answer worries me.
how can it be covered? How do you distinguish an elf loader application
(which just uses open + mmap after all) with... say a grep-calling perl
script?
As long as you allow apps to mmap (or even just read() a file into
memory).... they can start acting like an elf loader if they chose to do
so. And.. remember it's not the files WITH signature you're protecting
against (which you could check) but the ones WITHOUT. And there are many
of those; and you can't sign ALL files I think, not without going
through really great hoops anyway.
next prev parent reply other threads:[~2006-04-24 16:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 16:27 Makan Pourzandi (QB/EMC)
2006-04-24 16:47 ` Arjan van de Ven [this message]
2006-04-24 20:32 ` Nix
2006-04-24 20:45 ` Arjan van de Ven
2006-04-24 23:35 ` Nix
2006-04-25 6:30 ` Arjan van de Ven
2006-04-25 7:16 ` Nix
2006-04-25 16:11 ` Axelle Apvrille
2006-04-25 16:56 ` Arjan van de Ven
2006-04-25 18:57 ` Nix
2006-04-25 19:37 ` Arjan van de Ven
2006-04-25 19:52 ` Valdis.Kletnieks
2006-04-26 4:43 ` Kyle Moffett
2006-04-25 19:01 ` Chris Boot
2006-04-25 19:09 ` Valdis.Kletnieks
2006-04-25 20:00 ` Serge E. Hallyn
2006-04-28 15:33 ` Ulrich Drepper
2006-04-28 16:09 ` Serge E. Hallyn
2006-04-28 16:11 ` Arjan van de Ven
2006-04-28 16:29 ` Serge E. Hallyn
2006-04-28 17:53 ` Arjan van de Ven
2006-04-28 20:48 ` Michael Tokarev
2006-04-28 18:16 ` Christoph Hellwig
2006-04-28 19:22 ` Serge E. Hallyn
2006-04-25 13:00 ` Geert Uytterhoeven
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=1145897277.3116.44.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=axelle_apvrille@rc1.vip.ukl.yahoo.com \
--cc=disec-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=makan.pourzandi@ericsson.com \
--cc=serue@us.ibm.com \
/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
all inboxes | Powered by JetHome®