From: Adrian Bunk <bunk@stusta.de>
To: Alexander Wuerstlein <arw@arw.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signed binaries support [0/4]
Date: Thu, 21 Jun 2007 19:23:44 +0200 [thread overview]
Message-ID: <20070621172344.GQ12950@stusta.de> (raw)
In-Reply-To: <20070621162917.GB9741@cip.informatik.uni-erlangen.de>
On Thu, Jun 21, 2007 at 06:29:17PM +0200, Alexander Wuerstlein wrote:
> On 070621 18:19, Adrian Bunk <bunk@stusta.de> wrote:
> > On Thu, Jun 21, 2007 at 05:55:16PM +0200, Johannes Schlumberger wrote:
> >
> > > Hi,
> >
> > Hi Johannes,
> >
> > > We (two students of CS) built a system for signing binaries and verifying them
> > > before executing. Our main focus was to implement a way to inhibit execution
> > > of suid-binaries, which are not trustworthy (i.e. not signed).
> > >...
> >
> > doesn't anyone who is able to install a not trustworthy suid-binary
> > already have the priviliges to do anything he wants to without requiring
> > an suid bit?
>
> Yes, quite correct in most cases. But if you have taken control of a computer
> on of the more common ways to keep the control for some time is the
> installation of a suid-binary (e.g. as part of a rootkit).
There are so many ways for manipulating a computer that controlling
setuid binaries hardly brings a real security gain.
> One could also imagine a scenario where an attacker controls some filesystems
> (on external storage perhaps) where he can of course manipulate the suid bit,
> but he does not have direct control over the attacked system unless he can
> execute that file.
And unless the filesystem is mounted without nosuid...
> Ciao,
>
> Alexander Wuerstlein.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-06-21 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 15:55 [PATCH] signed binaries support [0/4] Johannes Schlumberger
2007-06-21 16:17 ` Adrian Bunk
2007-06-21 16:29 ` Alexander Wuerstlein
2007-06-21 17:23 ` Adrian Bunk [this message]
2007-06-21 17:34 ` Alexander Wuerstlein
2007-06-21 18:05 ` Adrian Bunk
2007-06-21 18:21 ` Johannes Schlumberger
2007-06-22 18:25 ` [PATCH] export xattr_resolve_name_sns [1/4] Alexander Wuerstlein
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
2007-06-22 18:25 ` [PATCH] sns: check related executable memory of binaries [3/4] Alexander Wuerstlein
2007-06-22 18:25 ` [PATCH] sns: add syscall to check signed state of a process [4/4] Alexander Wuerstlein
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=20070621172344.GQ12950@stusta.de \
--to=bunk@stusta.de \
--cc=arw@arw.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.