From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] ld.so.8: make lack of separator escaping explicit
Date: Tue, 6 Feb 2018 13:28:27 -0500 [thread overview]
Message-ID: <20180206182827.GH27582@vapier> (raw)
In-Reply-To: <5A796B65.7070705-fPG8STNUNVg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
On 06 Feb 2018 09:46, walter harms wrote:
> Am 05.02.2018 22:48, schrieb Mike Frysinger:
> > Make it clear that the delimiters in LD_PRELOAD, LD_LIBRARY_PATH, and
> > LD_AUDIT cannot be escaped so people don't try various methods (such
> > as \:) 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.
> > @@ -310,7 +311,8 @@ as shell variables!)
> > .B LD_PRELOAD
> > A list of additional, user-specified, ELF shared
> > objects to be loaded before all others.
> > -The items of the list can be separated by spaces or colons.
> > +The items of the list can be separated by spaces or colons,
> > +and there is no support for escaping either separator.
> > This can be used to selectively override functions in other shared objects.
> > The objects are searched for using the rules given under DESCRIPTION.
> > .IP
> > @@ -352,7 +354,8 @@ many obsolete or only for internal use.
> > A colon-separated list of user-specified, ELF shared objects
> > to be loaded before all others in a separate linker namespace
> > (i.e., one that does not intrude upon the normal symbol bindings that
> > -would occur in the process).
> > +would occur in the process)
> > +and there is no support for escaping the separator.
> > These objects can be used to audit the operation of the dynamic linker.
> > .IP
> > .B LD_AUDIT
>
> Everything is alright. NTL i would suggest to make consequences more clear, e.g.:
>
> "There is \fBno way\rR to have libraryname like libfoo-1:2. In this case ld.so will
> always search for \fBibfoo-1\fR and \fB2\fR."
could do. lets see what Michael thinks.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-06 18:28 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
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 [this message]
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=20180206182827.GH27582@vapier \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).