All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ld.so(8): make lack of separator escaping explicit
Date: Mon, 5 Feb 2018 16:44:55 -0500	[thread overview]
Message-ID: <20180205214455.GF27582@vapier> (raw)
In-Reply-To: <5A78842E.2060402-fPG8STNUNVg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

On 05 Feb 2018 17:19, walter harms wrote:
> Am 05.02.2018 17:13, schrieb Mike Frysinger:
> > Make it clear that the delimiters in LD_LIBRARY_PATH cannot be escaped
> > so people don't try various methods (like \:) to workaround it.
> > 
> > --- a/man8/ld.so.8
> > +++ b/man8/ld.so.8
> > @@ -271,7 +271,8 @@ This is useful when using a debugger.
> >  .B LD_LIBRARY_PATH
> >  A list of directories in which to search for
> >  ELF libraries at execution time.
> > -The items in the list are separated by either colons or semicolons.
> > +The items in the list are separated by either colons or semicolons,
> > +and there is no support for escaping either separator.
> >  Similar to the
> >  .B PATH
> >  environment variable.
> 
> I am not sure that i understand that. You say that a libname like
> libfoo.1.2:3 is unparseable ?

i think you're confusing LD_LIBRARY_PATH with other variables like
LD_PRELOAD.  my patch here is for the former, and that only loads
search paths (i.e. directories), not files.

however, you're correct in that LD_PRELOAD="libfoo.1.2:3" would not
work if the file was literally named "libfoo.1.2:3".  it would search
for "libfoo.1.2" and "3", and there is no way to change that behavior.

i'll send another patch.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-02-05 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 16:13 [PATCH] ld.so(8): make lack of separator escaping explicit Mike Frysinger
     [not found] ` <20180205161357.8131-1-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2018-02-05 16:19   ` walter harms
     [not found]     ` <5A78842E.2060402-fPG8STNUNVg@public.gmane.org>
2018-02-05 21:44       ` Mike Frysinger [this message]
2018-02-05 21:48   ` [PATCH v2] ld.so.8: " Mike Frysinger
     [not found]     ` <20180205214802.18397-1-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2018-02-06  8:46       ` walter harms
     [not found]         ` <5A796B65.7070705-fPG8STNUNVg@public.gmane.org>
2018-02-06 18:28           ` Mike Frysinger

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=20180205214455.GF27582@vapier \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wharms-fPG8STNUNVg@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.