mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de>
Cc: Alexander Wuerstlein <arw@arw.name>,
	linux-kernel@vger.kernel.org,
	Johannes Schlumberger <spjsschl@stud.informatik.uni-erlangen.de>
Subject: Re: [PATCH] Check files' signatures before doing suid/sgid [2/4]
Date: Thu, 21 Jun 2007 10:29:43 -0700	[thread overview]
Message-ID: <1182446983.2704.4.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070621172557.GE9741@cip.informatik.uni-erlangen.de>

On Thu, 2007-06-21 at 19:25 +0200, Alexander Wuerstlein wrote:
> On 070621 19:21, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Thu, 2007-06-21 at 18:02 +0200, Alexander Wuerstlein wrote:
> > > Modified task_struct to hold a 'signed flag' which is set on exec(), inherited
> > > on fork() and checked during exec before giving the new process suid/sgid
> > > privileges.
> > > 
> > 
> > 
> > 
> > do you also check the signature of glibc and every other shared library
> > that the app uses (or dlopens)? if not.. the entire exercise is rather
> > pointless...
> 
> We do check that, that is patch [3/4].
> 
> Of course we can only check mmap-ed files, if there is no file like with JIT
> compilers we are out of luck.

or if the process uses read() not mmap().

or .. or ...


so if perl is signed and it's the perl script that is setuid, and then
it includes other perl libs... that's read() not mmap().

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  reply	other threads:[~2007-06-21 17:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 16:02 Alexander Wuerstlein
2007-06-21 17:17 ` Arjan van de Ven
2007-06-21 17:25   ` Alexander Wuerstlein
2007-06-21 17:29     ` Arjan van de Ven [this message]
2007-06-21 17:46       ` Alexander Wuerstlein
2007-06-21 18:49         ` Arjan van de Ven
2007-06-21 21:40           ` Johannes Schlumberger
2007-06-23 18:01         ` Jan Engelhardt
2007-06-25 10:54           ` Johannes Schlumberger
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 15:55 [PATCH] signed binaries support [0/4] Johannes Schlumberger
2007-06-22 18:25 ` [PATCH] Check files' signatures before doing suid/sgid [2/4] Alexander Wuerstlein
2007-06-22 19:36   ` Satyam Sharma
2007-06-24 22:58     ` Alexander Wuerstlein
2007-06-25 23:53       ` Satyam Sharma
2007-06-26  0:27         ` Alexander Wuerstlein
2007-06-26  2:13           ` Satyam Sharma
2007-06-23 17:54   ` Jan Engelhardt

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=1182446983.2704.4.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=arw@arw.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snalwuer@cip.informatik.uni-erlangen.de \
    --cc=spjsschl@stud.informatik.uni-erlangen.de \
    /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®