All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Reiser <jreiser-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: build initramfs: uncontrolled LD_LIBRARY_PATH
Date: Thu, 18 Aug 2011 20:48:37 -0700	[thread overview]
Message-ID: <4E4DDD15.30202@bitwagon.com> (raw)

dracut uses ldd when building an initramfs, but I cannot find where
dracut controls LD_LIBRARY_PATH during the build.  Thus I do not trust
the results of ldd.  The string "LD_LIBRARY_PATH" does not appear
in the dracut source tree, there is no use of "env -i", dracut is
not setuid, etc.

At a minimum, the built initramfs could fail to satisfy some DT_NEEDED
entry during boot, leading to a crash.  Some soname was satisfied by
a library in a non-standard directory on the build-time LD_LIBRARY_PATH,
and was copied into that non-standard directory of the initramfs, but is
not findable using the boot-time (default standard) path list.

That might be the worst, because all users of the initramfs (namely:
booting only) do control LD_LIBRARY_PATH, so there might be "no possibility"
of substituting an actual non-standard library.  However, it would be
safer to control LD_LIBRARY_PATH while building initramfs, or at least
document why not.

-- 

             reply	other threads:[~2011-08-19  3:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  3:48 John Reiser [this message]
     [not found] ` <4E4DDD15.30202-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
2011-08-19  6:07   ` build initramfs: uncontrolled LD_LIBRARY_PATH Harald Hoyer
     [not found]     ` <4E4DFDB1.9090203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-19 16:18       ` John Reiser

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=4E4DDD15.30202@bitwagon.com \
    --to=jreiser-po6cbstgb2zwk0htik3j/w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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.