Le Sun, 27 Mar 2011 23:59:59 +0200 Denys Vlasenko <[email protected]> a écrit:
> On Sunday 27 March 2011 23:28, Seb wrote: > > Le Sun, 27 Mar 2011 22:16:29 +0200 > > Denys Vlasenko <[email protected]> a écrit: > > > > > Hmm. Can you run "strace -s99 -oLOG su - unibug" and post > > > resulting LOG file? > > > > Sure I can, attached. > > Your version of su passes wrong argv[0] to the shell: > > > execve("/bin/su", ["su", "-", "unibug"], [/* 37 vars */]) = 0 > ... > setgroups32(1, [1000]) = 0 > setuid32(1000) = 0 > chdir("/tmp") = 0 > open("/etc/environment", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or > directory) > close(3) = 0 > execve("/bin/ash", ["-su"], [/* 10 vars */]) = 0 > ^^^^^^^ > ???! > ... You'll see the same in the attached strace of a working /bin/ash, where I have just wiped out the pwdx applet. No way, it can't come from my su: I've previoulsy shown su was passing the right thing as argv[0], I encountered problem neither with bbx 1.18.4 (where visibly neither pstree nor pwd are implemented) nor with the rest of the software creation, and I in every way can't figure how a change in the code of busybox could affect my su... Sure it's tricky to understand, and "Seb is a dumb bunny running a crappy box" is a very rational and straightforward explanation which is worth the examination, but here it's IMHO just not enough to save phenomena... On the other hand, I'm running a rather uncommon bbx config, and I don't care of pstree/pwdx. So, maybe the wisest thing to do now is to wait and see if other issues occur, that can be connected with the kind of behaviour I describe. Take care, Seb.
LOG-noerr.gz
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
