Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@reciva.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: openembedded-devel@openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: TinyLogin
Date: Mon, 30 Mar 2009 12:12:14 +0100	[thread overview]
Message-ID: <1238411534.16991.120.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200903301254.51359.hs4233@mail.mn-solutions.de>

On Mon, 2009-03-30 at 11:54 +0100, Holger Schurig wrote:
> > - security auditing is difficult, since the large amount of
> > code-sharing in busybox makes it hard to determine which
> > functions can potentially be called from a setuid context;
> 
> Can I assume from this that you didn't actually look at busybox's 
> source-code?

No, I think you misunderstood what I meant.

The difficulty isn't in determining which applets will run as setuid; as
you say, that's straightforward to determine from the source code
(although not from the binary).  

The issue is that, since all the applets are linked together into one
monolithic binary, and hence have the ability in theory to call any
function in that binary, it is difficult to tell by looking at the
source code which functions might potentially be called (directly or
indirectly) by one of the setuid applets and hence would need to be
included in an audit for privilege-escalation vulnerabilities.

> Except that TinyLogin is end-of-life and won't get bugfixes from 
> upstream.

Yes, that's obviously the tradeoff.  Tinylogin is simple enough, though,
that fixing bugs locally would be easy enough if that became necessary.

p.





  reply	other threads:[~2009-03-30 11:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 21:15 TinyLogin Juan C. Villa
2009-03-28 21:54 ` TinyLogin Phil Blundell
2009-03-28 22:53   ` TinyLogin Denys Dmytriyenko
2009-03-29  9:00     ` TinyLogin Phil Blundell
2009-03-29  9:55       ` TinyLogin Koen Kooi
2009-03-30  8:53 ` TinyLogin Holger Schurig
2009-03-30  9:04   ` TinyLogin Koen Kooi
2009-03-30  9:18     ` TinyLogin Holger Schurig
2009-03-30 10:08       ` TinyLogin Phil Blundell
2009-03-30 10:54         ` TinyLogin Holger Schurig
2009-03-30 11:12           ` Phil Blundell [this message]
2009-03-30 11:33             ` TinyLogin Holger Schurig
2009-03-30 13:57               ` TinyLogin Mike (mwester)
2009-03-30 15:37                 ` TinyLogin Yuri Bushmelev
2009-03-31  9:45                   ` TinyLogin Phil Blundell
2009-03-30 10:15       ` TinyLogin Michael 'Mickey' Lauer

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=1238411534.16991.120.camel@mill.internal.reciva.com \
    --to=pb@reciva.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox