Hi,
On Sun, 25 Feb 2007 at 5:04 +0100, [EMAIL PROTECTED] wrote:
> Author: n0-1
> Date: 2007-02-25 05:04:23 +0100 (Sun, 25 Feb 2007)
> New Revision: 2097
>
> Modified:
> trunk/freewrt/package/busybox/ipkg/busybox.postinst
> Log:
> set the suid-bit of the busybox binary after installing from ipkg
>
> This should prevent disastrous situations after upgrading/reinstalling
> busybox for some reason and having logged out of the last root shell.
>
> Proof of concept:
> [EMAIL PROTECTED]:~# chmod u-s /bin/busybox
> [EMAIL PROTECTED]:~# ll /bin/busybox
> -rwxr-xr-x 1 root root 739224 Feb 25 01:29 /bin/busybox
> [EMAIL PROTECTED]:~# ipkg install busybox_1.4.1-6_mipsel.ipk
> Installing busybox (1.4.1-6) to root...
> Configuring busybox
> Done.
> [EMAIL PROTECTED]:~# ll /bin/busybox
> -rwsr-xr-x 1 root root 755724 Feb 25 04:55 /bin/busybox
>
> Maybe this should be done for freewrt_1_0 too?
Does this work for people trying to do an update on all supported
root filesystem types?
It is a bad idea to update busybox on squashfs-based root
filesystems, but if someone tries it, he should at least be able to
do it completely without a error message at the end or a
non-complete ipkg database. I am not sure what happens in this
situation.
bye
Waldemar
--
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
