From: Kyle Moffett <mrmacman_g4@mac.com>
To: Valdis.Kletnieks@vt.edu
Cc: Arjan van de Ven <arjan@infradead.org>, Nix <nix@esperi.org.uk>,
Axelle Apvrille <axelle_apvrille@yahoo.fr>,
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: Wed, 26 Apr 2006 00:43:07 -0400 [thread overview]
Message-ID: <E4450568-890D-4BD1-85AF-95BCB7F4978B@mac.com> (raw)
In-Reply-To: <200604251952.k3PJqj2J010248@turing-police.cc.vt.edu>
On Apr 25, 2006, at 15:52:45, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 25 Apr 2006 21:37:48 +0200, Arjan van de Ven said:
>> On Tue, 2006-04-25 at 19:57 +0100, Nix wrote:
>>> On Tue, 25 Apr 2006, Arjan van de Ven said:
>>>> so you didn't sign perl ? or bash ?
>>>
>>> You can write an elf loader in bash?!
>>
>> I've not tried it.. but afaics bash scripts are sufficiently
>> turing complete to pull it off ;)
>
> Well, somebody did 'shasm' (an assembler in bash), so I don't see
> any reason you can't do an elf loader... (OK, so you *might* have
> to write a machine emulator in bash, store the binary in an array,
> and emulate the sucker...)
Well I know that there are ways in Perl to overwrite arbitrary memory
(it's considered a bug of a certain XS library, although it has no
security implications because you could do the equivalent in Perl
anyways). I would assume that it's quite possible to do the same in
bash with a specially formatted bash script. Once you can scribble
on arbitrary memory, you can load a compiled ELF loader and execute
it without much trouble at all. A signed perl binary would open a
hole the size of a barn door in your scheme, I think.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2006-04-26 4:43 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
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 [this message]
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=E4450568-890D-4BD1-85AF-95BCB7F4978B@mac.com \
--to=mrmacman_g4@mac.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=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®