[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Some QA of Wheezy kfreebsd-amd64 binaries



Hi,

As a quick and random test, I installed all tasksel options of
kfreebsd-amd64, and executed each binary from {,/usr}/[s]bin as a
non-privileged user inside a jail.

Each was invoked without arguments, with stdin/out/err set to /dev/null,
a 5-second timeout and no network access.

Some results that may be of interest:

> pid 12584 (icontopbm), uid 1000: exited on signal 11
> pid 12669 (luit), uid 1000: exited on signal 11
> pid 13185 (python2.7), uid 1000: exited on signal 11
> pid 17279 (glxdemo), uid 1000: exited on signal 11
> pid 17347 (rletopnm), uid 1000: exited on signal 11
> pid 18058 (evolution-settings), uid 1000: exited on signal 5
> pid 18512 (umax_pp), uid 1000: exited on signal 11
> pid 21463 (xkbevd), uid 1000: exited on signal 11

python2.7 here referred to /usr/bin/system-config-printer, which crashes
when I run it normally (at least without X running).

These next two are odd, as they appear to be daemons running as uid 0.
This first one *may* have happened when I ran tasksel install:

> pid 8578 (packagekitd), uid 0: exited on signal 5

But this one was definitely triggered by something in /bin or /sbin
being run as uid 1000:

> pid 25310 (ck-collect-session-), uid 0: exited on signal 11

I also noted the exit codes.  An interesting one is 127:

> $ /usr/bin/guild
> /usr/bin/guild: 5: exec: /usr/bin/guile: not found

> $ /usr/bin/py3_compilefiles
> bash: /usr/bin/py3_compilefiles: /usr/bin/python3: bad interpreter: No such file or directory

> $ /usr/bin/xkeystone
> /usr/bin/env: nickle: No such file or directory

> $ /usr/bin/pkttyagent
> Error getting authority: Error initializing authority: Unexpected lack of content trying to read a line (g-io-error-quark, 0)

Then I ran ldd on each executable with some unexpected results:

> $ ldd /usr/bin/hipercdecode 
> ldd: exited with unknown exit code (138)

> $ ldd /usr/bin/inkscape
> ldd: exited with unknown exit code (139)

> $ ldd /usr/bin/inkview
> ldd: exited with unknown exit code (138)

That corresponds with this in dmesg:

> pid 16961 (ld-2.13.so), uid 1000: exited on signal 10
> pid 16964 (ld-2.13.so), uid 1000: exited on signal 11
> pid 16967 (ld-2.13.so), uid 1000: exited on signal 10

Although the binaries appear to be fine when I execute them (without X).

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org


Reply to: