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

> No, I think you misunderstood what I meant.

Okay.

> 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.

I'd have to cross-ref one specific busybox version with my 
specific .config file and look the call graph below the 
SUID-root applets. That would reveal if this is a substantial 
claim or just a fear.

But hey, I am among those people that didn't do a 
priviledge-escalation-verification of tinylogin. And so I'm not 
inclined to do that now for busybox --- it's not something that 
I care fore.  The usage-scenarios of my devices don't call for 
such measures.

However, I like to base fear on evidence, that's why I replied.


> > Except that TinyLogin is end-of-life and won't get bugfixes
> > from upstream.
>
> Yes, that's obviously the tradeoff.

The end-of-life argument is an argument for my 
paranoid-suggestion ("create a tinylogin_1.13.3_bb file with 
SRC_URI = busybox and a stripped down .config only for the 
tinylogin-equivalent-applets").


> Tinylogin is simple enough, though, that fixing bugs locally
> would be easy enough if that became necessary.

Your point <smile>

Let's wait (some more years) for the security assessment of 
tinylogin then <even bigger smile>.



  reply	other threads:[~2009-03-30 11:35 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           ` TinyLogin Phil Blundell
2009-03-30 11:33             ` Holger Schurig [this message]
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=200903301333.04881.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=pb@reciva.com \
    /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