From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Andreas Schwab <schwab@suse.de>,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] Improve DST handling (Bug 23102, Bug 21942, Bug 18018, Bug, 23259, CVE-2011-0536 ).
Date: Thu, 07 Jun 2018 12:16:00 -0000 [thread overview]
Message-ID: <afafa405-4546-e090-9f16-cde625e77480@redhat.com> (raw)
In-Reply-To: <e1c08bd2-2010-8ba9-5d44-6826aafe5bc5@redhat.com>
On 06/06/2018 10:18 PM, Carlos O'Donell wrote:
> +/* Process INPUT for DSTs and store in RESULT using the information from
> + link map L to resolve the DSTs. The value of START must equal the
> + start of the parent string if INPUT is a substring sequence being
> + parsed with path separators e.g. $ORIGIN:$PLATFORM. */
> char *
> -_dl_dst_substitute (struct link_map *l, const char *name, char *result)
> +_dl_dst_substitute (struct link_map *l, const char *start,
> + const char *input, char *result)
The comment should describe the storage requirements for RESULT.
I'm a bit worried about this:
else if (len != 0)
{
/* We cannot use this path element, the value of the
replacement is unknown. */
check_for_trusted = false;
wp = last_elem;
break;
}
Does this really do the right thing for $ORIGIN/../$LIB:/foo/$ORIGIN? I
would have expected a trusted path check for the first component in this
case.
Thanks,
Florian
next prev parent reply other threads:[~2018-06-07 12:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 5:03 Carlos O'Donell
2018-06-06 14:01 ` Florian Weimer
2018-06-06 14:55 ` Carlos O'Donell
2018-06-06 14:17 ` Florian Weimer
2018-06-06 15:59 ` Carlos O'Donell
2018-06-06 15:47 ` Andreas Schwab
2018-06-06 16:01 ` Carlos O'Donell
2018-06-06 16:10 ` Carlos O'Donell
2018-06-06 16:31 ` Andreas Schwab
2018-06-06 17:10 ` Carlos O'Donell
2018-06-06 17:28 ` Florian Weimer
2018-06-06 18:49 ` Carlos O'Donell
2018-06-06 18:56 ` Florian Weimer
2018-06-06 20:04 ` Carlos O'Donell
2018-06-07 6:49 ` Andreas Schwab
2018-06-08 2:08 ` Carlos O'Donell
2018-06-11 8:04 ` Andreas Schwab
2018-06-12 3:08 ` Carlos O'Donell
2018-06-12 7:31 ` Andreas Schwab
2018-06-12 12:46 ` Carlos O'Donell
2018-06-12 13:02 ` Andreas Schwab
2018-06-12 13:03 ` Carlos O'Donell
2018-06-06 20:19 ` Carlos O'Donell
2018-06-07 11:38 ` Florian Weimer
2018-06-08 2:14 ` Carlos O'Donell
2018-06-07 12:16 ` Florian Weimer [this message]
2018-06-08 4:15 ` Carlos O'Donell
2018-06-08 5:21 ` Florian Weimer
2018-06-08 5:46 ` Carlos O'Donell
2018-06-08 5:50 ` Carlos O'Donell
2018-06-07 12:43 ` Florian Weimer
2018-06-08 5:37 ` Carlos O'Donell
2018-06-08 5:45 ` [PATCH v4] " Carlos O'Donell
2018-06-08 5:51 ` Florian Weimer
2018-06-08 6:03 ` Carlos O'Donell
2018-06-08 6:25 ` Florian Weimer
2018-06-11 2:55 ` Carlos O'Donell
2018-06-11 7:28 ` Florian Weimer
2018-06-11 14:44 ` Carlos O'Donell
2018-06-12 3:46 ` Carlos O'Donell
2018-06-12 13:08 ` [PATCH v6] " Carlos O'Donell
2018-06-12 13:20 ` Andreas Schwab
2018-06-12 13:23 ` Andreas Schwab
2018-06-12 14:10 ` Carlos O'Donell
2018-06-12 14:34 ` Andreas Schwab
2018-06-12 14:31 ` Florian Weimer
2018-06-12 14:36 ` Carlos O'Donell
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=afafa405-4546-e090-9f16-cde625e77480@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).