Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Yuri Bushmelev <jay4mail@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TinyLogin
Date: Mon, 30 Mar 2009 19:37:29 +0400	[thread overview]
Message-ID: <200903301937.29417.jay4mail@gmail.com> (raw)
In-Reply-To: <49D0CFC7.9090902@dls.net>

Hello!

> IMO (for what that's worth), we need to support the "everything is
> busybox!" sort of build; there's just no alternative for small devices.
>  But the problem is what do we do for that middle ground, for devices
> that can't fit the entire set of "proper" tools but might not be willing
> to take the security risk associated with running busybox SETUID.

Can we build two busybox'es? One with ordinary non-suid-tools and one with 
all suid? Is it crazy idea? :)

Can someone look here for login replacement (about using on Linux):
http://www.freebsd.org/cgi/cvsweb.cgi/src/release/picobsd/tinyware/login/

and may be here for some other tools:
http://www.freebsd.org/cgi/cvsweb.cgi/src/release/picobsd/tinyware/

-- 
Yuri Bushmelev



  reply	other threads:[~2009-03-30 15:39 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             ` TinyLogin Holger Schurig
2009-03-30 13:57               ` TinyLogin Mike (mwester)
2009-03-30 15:37                 ` Yuri Bushmelev [this message]
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=200903301937.29417.jay4mail@gmail.com \
    --to=jay4mail@gmail.com \
    --cc=openembedded-devel@lists.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