From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Fix busybox SUID support
Date: Wed, 24 Feb 2010 11:19:16 +0100 [thread overview]
Message-ID: <201002241119.20053.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <1266951776.18176.47.camel@trini-m4400>
[-- Attachment #1: Type: Text/Plain, Size: 1013 bytes --]
Dnia wtorek, 23 lutego 2010 o 20:02:56 Tom Rini napisał(a):
> I was about to just push this and I noticed that a number of
> distributions (SlugOS, Angstrom, Kaelios, micro) currently set
> FEATURE_SUID=y, but it's not actually install SUID. And since I recall
> some way-back-when's of "busybox SUID is dangerous / crap!", I thought
> it best to post the patch first and let folks speak up / ask me to drop
> FEATURE_SUID=y when I do this. So, here's the patch:
Ok, but does not it require /etc/something to list which applets are allowed
to be suid and which are not?
Hm. checked sources. with FEATURE_SUID suid will be active only for "crontab,
dnsd, findfs, ipcrm, ipcs, login, passwd, ping, su, traceroute, vlock"
commands. /etc/busybox.conf is CONFIG_FEATURE_SUID_CONFIG option.
Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-02-24 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 19:02 [PATCH] Fix busybox SUID support Tom Rini
2010-02-23 19:51 ` Khem Raj
2010-02-23 20:14 ` Tom Rini
2010-02-23 20:23 ` Chris Larson
2010-02-23 21:37 ` Phil Blundell
2010-02-23 22:52 ` Michael 'Mickey' Lauer
2010-02-23 23:01 ` Tom Rini
2010-02-24 10:19 ` Marcin Juszkiewicz [this message]
2010-02-24 16:10 ` Tom Rini
2010-02-26 15:43 ` Mike Westerhof
2010-02-26 18:20 ` Koen Kooi
2010-02-26 20:21 ` C Michael Sundius
2010-02-26 22:26 ` Bernhard Reutner-Fischer
2010-02-26 22:42 ` Phil Blundell
2010-02-26 23:06 ` Bernhard Reutner-Fischer
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=201002241119.20053.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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