From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Jan Hubicka" <hubicka@ucw.cz>,
"Rafael Espíndola" <rafael.espindola@gmail.com>,
"Renato Golin" <renato.golin@linaro.org>, gcc <gcc@gcc.gnu.org>
Subject: Re: Fwd: LLVM collaboration?
Date: Wed, 12 Feb 2014 16:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1402121617330.5339@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFiYyc0ttm34x6poZPg5kiSH78iUbyjRrb6y+WrhpOGQjWHz9g@mail.gmail.com>
On Wed, 12 Feb 2014, Richard Biener wrote:
> What about instead of our current odd way of identifying LTO objects
> simply add a special ELF note telling the linker the plugin to use?
>
> .note._linker_plugin '/...../libltoplugin.so'
>
> that way the linker should try 1) loading that plugin, 2) register the
> specific object with that plugin.
Unless this is only allowed for a whitelist of known-good plugins in
known-good directories, it's a clear security hole for the linker to
execute code in arbitrary files named by linker input. The linker should
be safe to run on untrusted input files.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-02-12 16:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMSE1kdfpeLp6NEc+jnEWqi0KWV-+=Q701UsiLhgcn13X6fYcA@mail.gmail.com>
2014-02-07 21:34 ` Renato Golin
2014-02-07 21:53 ` Diego Novillo
2014-02-07 22:07 ` Renato Golin
2014-02-07 22:33 ` Andrew Pinski
2014-02-07 22:35 ` Renato Golin
2014-02-10 14:48 ` Diego Novillo
2014-02-07 22:28 ` Andrew Pinski
2014-02-07 22:23 ` Andrew Pinski
2014-02-07 22:42 ` Jonathan Wakely
2014-02-07 23:12 ` Renato Golin
2014-02-07 23:30 ` Fwd: " Joseph S. Myers
2014-02-07 23:59 ` Renato Golin
2014-02-11 2:29 ` Jan Hubicka
2014-02-11 9:55 ` Renato Golin
2014-02-11 10:03 ` Uday Khedker
2014-02-11 16:00 ` Jan Hubicka
2014-02-11 16:07 ` Uday Khedker
2014-02-11 16:18 ` Renato Golin
2014-02-11 17:29 ` Renato Golin
2014-02-11 18:02 ` Rafael Espíndola
2014-02-11 18:51 ` Markus Trippelsdorf
2014-02-11 20:52 ` Jan Hubicka
2014-02-11 21:20 ` Jan Hubicka
2014-02-11 21:38 ` Rafael Espíndola
2014-02-11 22:36 ` Hal Finkel
2014-09-17 21:41 ` Hal Finkel
2014-02-12 11:10 ` Fwd: " Richard Biener
2014-02-12 13:15 ` Rafael Espíndola
2014-02-12 16:19 ` Joseph S. Myers [this message]
2014-02-12 16:23 ` Jan Hubicka
2014-02-13 9:06 ` Richard Biener
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=Pine.LNX.4.64.1402121617330.5339@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rafael.espindola@gmail.com \
--cc=renato.golin@linaro.org \
--cc=richard.guenther@gmail.com \
/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).