From: John Stile <john@stilen.com>
To: buildroot@busybox.net
Subject: [Buildroot] how does buildroot avoid requireing root?
Date: Fri, 28 Jun 2013 17:47:16 -0700 [thread overview]
Message-ID: <1372466836.28302.157.camel@localhost> (raw)
I am confused about how buildroot creates busybox.
There are notes that one must ensure that busybox setuid root.
Performing this operation must be performed as root:
chown 0.0 /bin/busybox; chmod 4755 /bin/busybox
Yet when I use buildroot I never become root.
How does buildroot accomplish this?
In output/build/busybox-1.18.5 I see applets/install.sh calls:
install -m 755 busybox $prefix/bin/busybox || exit 1
but I don't see how this becomes setuid?
On my embedded system, I see:
-rwsr-xr-x 1 root root 605876 Jun 28 2013 /bin/busybox*
next reply other threads:[~2013-06-29 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 0:47 John Stile [this message]
2013-06-29 1:49 ` [Buildroot] how does buildroot avoid requireing root? Charles Krinke
2013-06-29 8:49 ` Thomas Petazzoni
2013-06-29 17:08 ` John Stile
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=1372466836.28302.157.camel@localhost \
--to=john@stilen.com \
--cc=buildroot@busybox.net \
/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