Re: [OpenWrt-Users] su utility in OpenWRT "White Russian" release
Hello Martin, Am Sat, 28 Jan 2017 01:21:41 +0200 schrieb Martin T: > [..] > Or maybe there is some smarter way? could a simple "ssh root@localhost" solve your problem? Maybe add an alias, if you really insist on typing "su"? Cheers, Lars ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
Re: [OpenWrt-Users] su utility in OpenWRT "White Russian" release
Problem is, that this White Russian router is in another country :) I can't upgrade this. Hardware is WRT54GS. I downloaded OpenWrt-SDK-Linux-i686-1.tar.bz2(http://downloads.openwrt.org/whiterussian/0.9/OpenWrt-SDK-Linux-i686-1.tar.bz2), but I'm not sure if I should try to build entire coreutils or is it possible also to simply compile the su binary. Martin On Sat, Jan 28, 2017 at 3:56 PM, Aaron Zwrote: > On Sat, Jan 28, 2017 at 8:48 AM, Aaron Z wrote: >> On Sat, Jan 28, 2017 at 7:10 AM, Martin T wrote: >>> I need to enable non-root users to log into the router and if needed, >>> execute su to become a root user. >> What hardware is it running on? Will it handle a newer firmware >> (perhaps the LEDE 17.0.1 that is in release testing now?). >> I dont think su can be easily be backported to White Russian... > > Correction, LEDE is/will be 17.01, I put an extra period in the version. > > Aaron Z > A human being should be able to change a diaper, plan an invasion, > butcher a hog, conn a ship, design a building, write a sonnet, balance > accounts, build a wall, set a bone, comfort the dying, take orders, > give orders, cooperate, act alone, solve equations, analyze a new > problem, pitch manure, program a computer, cook a tasty meal, fight > efficiently, die gallantly. Specialization is for insects. > — Robert Heinlein, Time Enough for Love ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
Re: [OpenWrt-Users] su utility in OpenWRT "White Russian" release
On Fri, Jan 27, 2017 at 6:21 PM, Martin Twrote: > I have an OpenWRT router with "White Russian" release in remote > location. It has no "su" command and if I inspect the > package/busybox/config/loginutils/Config.in file in > http://downloads.openwrt.org/whiterussian/0.9/whiterussian-0.9.tar.bz2, > then looks like BusyBox was compiled without "su" command. IIRC, OpenWRT runs everything (or most everything) from the shell as root, so su is not needed. Is there something you are doing that needs su to work? Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
[OpenWrt-Users] su utility in OpenWRT "White Russian" release
Hi, I have an OpenWRT router with "White Russian" release in remote location. It has no "su" command and if I inspect the package/busybox/config/loginutils/Config.in file in http://downloads.openwrt.org/whiterussian/0.9/whiterussian-0.9.tar.bz2, then looks like BusyBox was compiled without "su" command. In addition, there seems to be no "coreutils-su" package for "White Russian" as there is for example for "Backfire"( OpenWRT 10.03). I installed OpenWRT "Backfire" to identical router and installed the coreutils-su_7.2-1_brcm47xx.ipk package and then copied /usr/bin/su to this remote "White Russian" router. While the binary architecture should be correct, it does not run: root@wr:~# /usr/bin/su /usr/bin/su: symbol 'stdout': can't handle reloc type 0x7e root@wr:~# Error above should indicate to library issues. According to ldd "su" binary requires following libraries: libcrypt.so.0 => /lib/libcrypt.so.0 (0x2aabe000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2aae2000) libc.so.0 => /lib/libc.so.0 (0x2ab02000) ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x2aaa8000) In "Backfire", where "su" binary was copied from, they have following versions: libcrypt-0.9.30.1.so libgcc_s.so.1 libuClibc-0.9.30.1.so ld-uClibc-0.9.30.1.so In "White Russian" they have following versions: libcrypt-0.9.27.so libgcc_s.so.1 libuClibc-0.9.27.so ld-uClibc-0.9.27.so I guess it is not safe to simply copy newer libraries into the "White Russian" router as it might break some programs. Should I install OpenWRT "White Russian" to this spare router and try to copile coreutils or coreutils-su there and then again copy the su binary into this remote router? If yes, then which coreutils or coreutils-su source version should I use in order to compile the su binary? I looked into https://github.com/openwrt/packages/tree/master/utils, but didn't find anything suitable. Or maybe there is some smarter way? thanks, Martin ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users