Re: [PATCH v2] ld.so.8: make lack of separator escaping explicit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/06/2018 07:28 PM, Mike Frysinger wrote:
> 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.

I'm inclined to think we don't need to be more explicit, since it is a rather 
unusual thing to create files with names containing [;:].

Cheers,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux