mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Axelle Apvrille <axelle_apvrille@yahoo.fr>
Cc: Nix <nix@esperi.org.uk>,
	drepper@gmail.com, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	disec-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] Release Digsig 1.5: kernel module for run-timeauthentication of binaries
Date: Tue, 25 Apr 2006 18:56:40 +0200	[thread overview]
Message-ID: <1145984201.3114.34.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060425161139.87285.qmail@web26109.mail.ukl.yahoo.com>

On Tue, 2006-04-25 at 18:11 +0200, Axelle Apvrille wrote:
> Hi all,
> 
> Just my few cents on signed binaries and DigSig. It's
> kind of a very partial reply to several parts of
> various emails (Arjan, Ulrich, Nix ...), sorry for
> that ;-)
> 
> 1- "does this also prevent people writing their own
> elf loader in a bit of perl and just mmap the code"
> 
> I'm not sure to exactly understand what you mean:
> 
> - if you mean writing an application able to read &
> 'interpret' an ELF executable: again, I think DigSig
> will prevent this, because when you mmap the code,
> this calls (at kernel level) do_mmap which triggers an
> LSM hook called file_mmap. And we implement checks in
> that hook...

this is not correct, you don't need mmap you can do a read just fine as
well.


> - finally, note you also have choice not to sign this
> elf loader of yours. If it isn't signed, it won't ever
> run ;-)

so you didn't sign perl ? or bash ?




  reply	other threads:[~2006-04-25 16:56 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
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 [this message]
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=1145984201.3114.34.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=axelle_apvrille@yahoo.fr \
    --cc=disec-devel@lists.sourceforge.net \
    --cc=drepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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®