From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] sudo: error while loading shared libraries
Date: Thu, 6 May 2021 21:37:44 +0200 [thread overview]
Message-ID: <20210506213744.3c03ca12@gmx.net> (raw)
In-Reply-To: <AM0PR06MB5923358E8BAADC4FAA9F5542C0589@AM0PR06MB5923.eurprd06.prod.outlook.com>
Hello Uwe,
On Thu, 6 May 2021 11:34:13 +0000, Uwe Fechner <uwe.fechner@nl.abb.com> wrote:
> Dear all,
>
> I fixed the problem with sudo by adding the following symlink:
>
> [/lib]$ ls -la libsudo_util.so.0
> lrwxrwxrwx 1 root root 35 May 5 18:28 libsudo_util.so.0 -> /usr/libexec/sudo/libsudo_util.so.0
>
> But this is more a workaround.
>
> readelf -d sudo
> has the following output:
>
> Dynamic section at offset 0x20b14 contains 34 entries:
> Tag Type Name/Value
> 0x00000001 (NEEDED) Shared library: [libutil.so.1]
> 0x00000001 (NEEDED) Shared library: [libsudo_util.so.0]
> 0x00000001 (NEEDED) Shared library: [libpthread.so.0]
> 0x00000001 (NEEDED) Shared library: [libdl.so.2]
> 0x00000001 (NEEDED) Shared library: [libc.so.6]
> 0x00000001 (NEEDED) Shared library: [ld-linux-armhf.so.3]
> 0x0000001d (RUNPATH) Library runpath: [libexec/sudo]
> 0x0000000c (INIT) 0x2f1c
>
> The library runpath is wrong, it should be /usr/libexec/sudo .
>
> Or the package sudo should install libsudo_util.so.0 in the folder /lib.
>
> My conclusion is that there is a bug in the package sudo, version 1.9.5p2 .
>
> Any comments?
Please provide the output of the following commands (example output given):
$ rm -rf build/sudo-1.9.5p2
$ make sudo 2>&1 | grep rpath | tail -1
libtool: link: <your_build_path>/host/bin/aarch64-buildroot-linux-gnu-gcc -o sudo conversation.o copy_file.o edit_open.o env_hooks.o exec.o exec_common.o exec_monitor.o exec_nopty.o exec_pty.o get_pty.o hooks.o limits.o load_plugins.o net_ifs.o parse_args.o preserve_fds.o signal.o sudo.o sudo_edit.o tcsetpgrp_nobg.o tgetpass.o ttyname.o utmp.o -Wl,--enable-new-dtags -Wl,-z -Wl,relro -fstack-protector-strong -lutil ../lib/util/.libs/libsudo_util.so -lpthread -ldl -Wl,-rpath -Wl,<your_build_path>/build/sudo-1.9.5p2/lib/util/.libs -Wl,-rpath -Wl,/usr/libexec/sudo
$ readelf -d ./target/usr/bin/sudo | grep RUNPATH
0x000000000000001d (RUNPATH) Library runpath: [<your_build_path>/build/sudo-1.9.5p2/lib/util/.libs:/usr/libexec/sudo]
$ make > /dev/null 2>&1
$ readelf -d ./target/usr/bin/sudo | grep RUNPATH
0x000000000000001d (RUNPATH) Library runpath: [/usr/libexec/sudo]
Just to check if the rpath is corrupted from start/compile on or if it is
a problem of the buildroot sanitizing rpath step (or some funny problem
with your local build path)...
Regards,
Peter
>
> Uwe
> ________________________________
> From: buildroot <buildroot-bounces@busybox.net> on behalf of Uwe Fechner <uwe.fechner@nl.abb.com>
> Sent: Wednesday, May 5, 2021 1:14 PM
> To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: buildroot at busybox.net <buildroot@busybox.net>
> Subject: Re: [Buildroot] sudo: error while loading shared libraries
>
> This email originated from outside of your organization. Please do not click on links or open attachments unless you recognize the sender and know the content is safe.
>
> Dear Thomas,
>
> Thanks for looking into this issue, but your suggestion did not help:
>
> $ LD_LIBRARY_PATH=/usr/libexec/sudo sudo dmesg
> sudo: error while loading shared libraries: libsudo_util.so.0: cannot open shared object file: No such file or directory
>
> Any other idea?
>
> Uwe
> ________________________________
> From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Sent: Tuesday, May 4, 2021 9:43 PM
> To: Uwe Fechner <uwe.fechner@nl.abb.com>
> Cc: buildroot at busybox.net <buildroot@busybox.net>
> Subject: Re: [Buildroot] sudo: error while loading shared libraries
>
> This email originated from outside of your organization. Please do not click on links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Hello Uwe,
>
> On Tue, 4 May 2021 11:18:59 +0000
> Uwe Fechner <uwe.fechner@nl.abb.com> wrote:
>
> > Hello,
> >
> > we are using buildroot on i.mx6 since a long time.
> >
> > Since yesterday I get the following error with the sudo package:
> >
> > sudo dmesg
> > sudo: error while loading shared libraries: libsudo_util.so.0: cannot open shared object file: No such file or directory
> >
> > We are using sudo-1.9.5p2 .
> >
> > The library exists and the permissions seem to be correct:
> >
> >
> > ls -la /usr/libexec/sudo
>
> Based on the error message, it seems like the library is not dlopen()ed
> but directly linked into sudo. Hwoever, /usr/libexec/sudo is not in the
> default search path for libraries, and therefore unless the sudo binary
> has a RPATH/RUNPATH pointing to /usr/libexec/sudo, I believe what
> you're seeing is expected.
>
> To verify this, you can try:
>
> LD_LIBRARY_PATH=/usr/libexec/sudo sudo dmesg
>
> Really, I think libsudo_util.so has no business in /usr/libexec/sudo,
> it should be in /usr/lib. Based on the names of the other .so files,
> they look like dlopen()ed libraries, which can stay in
> /usr/libexec/sudo.
>
> > total 588
> > drwxr-xr-x 2 root root 4096 May 3 19:31 .
> > drwxr-xr-x 11 root root 4096 May 3 19:31 ..
> > -rw-r--r-- 1 root root 17716 May 3 19:31 audit_json.so
> > -rw-r--r-- 1 root root 9380 May 3 19:31 group_file.so
> > lrwxrwxrwx 1 root root 21 May 3 19:31 libsudo_util.so -> libsudo_util.so.0.0.0
> > lrwxrwxrwx 1 root root 21 May 3 19:31 libsudo_util.so.0 -> libsudo_util.so.0.0.0
> > -rwxr-xr-x 1 root root 112412 May 3 19:31 libsudo_util.so.0.0.0
> > -rw-r--r-- 1 root root 5284 May 3 19:31 sample_approval.so
> > -rw-r--r-- 1 root root 420184 May 3 19:31 sudoers.so
> > -rw-r--r-- 1 root root 5260 May 3 19:31 sudo_noexec.so
> > -rw-r--r-- 1 root root 5276 May 3 19:31 system_group.so
> >
> > Any idea?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=04%7C01%7Cuwe.fechner%40nl.abb.com%7Ce7e4cd3c187e43ca459c08d90f34d801%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C637557541905702900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xTDZlOO1mFKWSYRVNADflI0hh2%2F9CTbkVBOKIYIztHg%3D&reserved=0<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&data=04%7C01%7Cuwe.fechner%40nl.abb.com%7C707d6d31efc14d10bd8c08d90fb7052a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C637558102642959557%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=4zK1AHuHJBvpTeAUKNN%2BvgqAo9eRMi5FCGqnPjbG3Z8%3D&reserved=0>
next prev parent reply other threads:[~2021-05-06 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 11:18 [Buildroot] sudo: error while loading shared libraries Uwe Fechner
2021-05-04 19:43 ` Thomas Petazzoni
2021-05-05 11:14 ` Uwe Fechner
2021-05-05 18:52 ` Arnout Vandecappelle
2021-05-06 11:34 ` Uwe Fechner
2021-05-06 19:37 ` Peter Seiderer [this message]
2021-05-10 13:10 ` Uwe Fechner
2021-05-12 17:17 ` Peter Seiderer
2021-05-17 17:39 ` Arnout Vandecappelle
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=20210506213744.3c03ca12@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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