From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] sudo: error while loading shared libraries
Date: Tue, 4 May 2021 21:43:06 +0200 [thread overview]
Message-ID: <20210504214306.378dbbaf@windsurf> (raw)
In-Reply-To: <AM0PR06MB5923A441CD0C1EF1952FC031C05A9@AM0PR06MB5923.eurprd06.prod.outlook.com>
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://bootlin.com
next prev parent reply other threads:[~2021-05-04 19:43 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 [this message]
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
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=20210504214306.378dbbaf@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.